Selling Access database - How do I ensure user has valid license?

[darlingm]

I am developing an Access database, and using the Access 2007 Developer Extensions to "compile" it into an installable program which includes the freely distributable Access 2007 RunTime, for users who don't have it already installed.

I am planning on charging a subscription fee to use my Access database. Are there any existing method for handling making sure the user's subscription is still active, and if not, either locking them our or preferably making everything read-only? If there aren't any existing methods anyone can point me to, does anyone have any ideas?

I plan on being the person who installs the application the first time, however I'm sure instances will come up where I instead mail the user a CD for them to install.

Regardless of whether I complete the first install, I'm not interested in going to each users' location periodically regarding the subscription.

I'm more interested in going the route of the user typing in some type of registration code, which is validated for read/write access for a period of time.

I don't want to rely on the user having an internet connection, but if they had one, I could certainly go the Microsoft model (try internet verification, if it goes wrong or there isn't a connection, have user call in.)

 

[neileg]

Never done it, but I'm sure there are third party products you can buy that add this functionality to Access.

 

[gemma-the-husky]

i'm sure you are aware, but when you distribute an app as runtime, you lose all the functionality of the access environment - sorts/binoculars etc - you have to program all the functionality yourself.

in many ways its better to distribute an mde. to clients who have access.

you still have the same issueswrt registration though