Secure a database on a CD.

[Michael]

I forget how to do this. I have created a database that I use for a website
that controls the delivery of products. I have someone who may be interested
in buying the system to use as a stand alone application. I need to provide
them with a sample, but I do not want to give them the database in any form
that they can copy my tables and query's. I know there is a way.. just
cannot remember.
Thanks
Michael

 

[TC]

What do you actually want to do?

1. stop them copying the data out from your tables?

2. stop them copying the design of your queries, forms, reports & modules?,
or

3. stop them copying your demo system & using it for ever after?

For 1, you'd have to use Access security. However, in my opinion, the >user<
owns the data that he keys in to the system - not the developer. So it is
inappropriate to stop the users copying data. An exception would be, if the
system came pre-set with proprietary data that >you< created, not the user.

For 2., just supply the database in MDE format.

For 3, maybe check the current date in the database's startup code. If it is
more than 30 days since you supplied the system, just quit the system. This
is a crude method, it can be defeated by the user setting their clock
backwards, & it is no good if you provide example databases to many
customers (because then, the cut-off date would have to be altered for each
database). Make the database an MDE so the user can not delete the checking
code.

If the user then wants to purchase your system, remember you will have to
split it into a "front end/back end" structure, so you can provide him with
updates. If you do not do that, it will be difficult to supply him with
updates, because if you give him a new copy of your database, this will not
contain his current data, so if he installs that copy, he will lose his
current data!

HTH,
TC

 

[Michael]

Thanks TC.
I am providing the program to a software house that has expressed an
interest in marketing it.

So my interest is in keeping them from copying the design of your queries,
forms, reports & modules. So .mde is the way to go. It took me a year to
build the system and I want to protect my work. I have not worked in Access
in about a year (after that last project I needed a break) and have
forgotten just about everything..
thanks for you help
Michael