Limited Records in Demo Datbase

Topic

New Reply

I have a client who I want to send a “working” demo copy of a database. To protect my investment time as much as possible, I would like to limit the number of “new” records he can enter (probably 50). This would allow him to try out the functionality, etc. without hopefully him deciding to keep a “copy” for himself and then returning the demo copy as “not interested”. I am also employing the Shift-Key disable coding which should limit his abilities even a little more.

It seems as if I’ve never had to worry about “limiting” the number of new record entries before, so this is something new for me. Thanks for the help Lounge Rangers.

Reply | Quote

Replies

A little devious, but if using a form, you could add a little check after each update. Query the data table, tally the record count, and if the count exceeds your 50 record limit, delete a record from the table. Delete the first, last, or (insert evil laugh here) random record. This works best if the table has an autonumber or other numeric key to sort & select from.

Let your prospective client enter all the data that they want, but they will not be able to exceed your set limit, and the more data that they do enter after reaching this limit, the more useless their data will become. Just make sure that they know the limit is in place before they accuse you of shoddy programming.

Reply | Quote

Also, you could convert the database to an MDE file before sending. This will prevent them from viewing the design of any form, report, or module (which includes blocking them from viewing the code you’ve used for forms and reports).

Muuhahahahaha!!!!

Reply | Quote