Scenario
Am building a dynamic date driven environment using asp and an MSAccess 2003 database. The resulting pages and database to be marketed to potential clients.

Problem
I want to prevent the client from opening the MSAccess 2003 database in order to ensure that the intellectual property rights and investment in the database design itself are restricted. I know that an MSAccess database can be password protected however this prevents the data access pages from retrieving/sending data to the MSAccess database.

Solution
Any ideas?

Thank you in anticipation of quality assistance and advice.

Hi

Probably the best/most secure way is to handle all your DB connections from within a compiled VB6 or other DLL file which you then call from the ASP page. Only disadvantage is that it ads a whole new dimension of complexity to your application. (Esp with recordsets & Array's etc)

The other option is - if you planning to distribute this web app I would assume you would wanna use some kind of "Installer" (Like Ino Setup Installer) to package your solution for instalation on the webserver. You could use this "Installer" to create a ODBC Connection on the server to the DB and setting the passwords you used in your DB etc.

Sorry for the High Level Answer but I have not got anything aff-hand that I have used. Gimme a shout if u need more info.

Regards
Marnus