Hi, Paul.
How can this be done?
With quite a bit of effort on your part, whereby the customer sets his
system clock back before the expiration date every time he wants to use your
application so that he can use it indefinitely. A better way to limit a
database application as a demo is to limit the number of records in the most
important tables, implement User-Level Security so that the customer can't
create new tables and relink to them, nor create new queries, especially
UNION queries where an aggregate of tables would otherwise be used to bypass
the record number limit.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs:
www.DataDevilDog.BlogSpot.com,
www.DatabaseTips.BlogSpot.com http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"Paul H" <pa**@nospam.comwrote in message
news:A5******************************@eclipse.net. uk...
>A client wants me to develop a db that he will sell on to other people. He
wants to allow them to run the database for 30 days then lock them out if
they chose not to buy the database.
The database will be an MDE file. A typical scenario might be:
1. The user trials the database and inputs some data.
2. The trial period ends and the user is locked out.
3. The user pays us and we send him an unlock code so that he can reopen
the database with all of his data intact.
How can this be done?
Paul