one point access to access database

[sqlnerd]

Hi there!

My access database is part of a web application. The application will run from my client's server once installed (that is copied to the client's server and virtual directory created). I want to protect my database at client's server. I want to ensure that my application running at the client's place should be the only access point to the database. The client should not be able to open the database or even read the tables through any other appln. such as word, excel.

I have tried the following but in vain

1. setting password to the database... this is not fool proof. The Mailmerge facility in Word can still fetch the info from the database even if can not modify the data.

2. Encrypting the database does not solve the problem, too.

Is there any packaging mechnaism that makes my database fool proof.. or should i write my own encrypting/decrypting mechanism

Pl. help

SQLNerd

 

[HomeALone]

Have you tried making your database into MDE file before you send to your client. Check out this feature and I am sure it will do the trick for you. Good luck!

 

[sqlnerd]

Hi HomeAlone,

Thanks for your timely reply. But, I have tried the MDE option also. I tried it again after your reply, just in case. But, this is not preventing me from accessing the encrypted database, my friend. My original database is password protected. When I make an MDE out of it, it inherits the password protection from the original file. But thats the only thing it does. It works, in all other aspects, like the original one. I can still open a table, modify the data and so on.

I think the MDE is primarily for protecting modules as the Access documentation says. I wonder if it will protect my tables also. I am not using Access modules since my code is purely ASP and I only store data in Access tables.

Will MDE work still? Did I miss anything with MDE... pl. clarify.