[AccessD] Copy Protection Needed

I do think this is the ticket for instances where you do not care how many copies run at a given 
site.  Make the user contact you for a key.  Make them include the "serial number" of the installed 
BE and the name of the company and create a table that holds the name / address of the company and 
keys dispensed.  Then if people call in asking for more / new keys, the Serial Number of the BE 
should match the name / address they provide.  If the serial number is in your database but the name 
/ address is somewhere completely different...

Is anyone interested in forming a working group to define and perhaps even design / build such a 
system that Database Advisors could license to group members?

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
> Susan,
> I would store it in a User Defined Property on the BE and the FE.  The UDP
> would store BE HD Srl No.  (Plus anything else you want to create info for,
> eg Date installed, Company Licensed to, etc, etc).
> 
> Each time the BE fires up it checks the HD Srl No.  Each time the FE fires
> up it checks the entries on the BE - it also increases the number of logged
> users by 1 and checks if they have reached the licensed limit.  You can also
> limit the number of installations this way.  
> 
> Make use of the UDP to store and record all sorts of stuff.  Limited only by
> your imagination and your needs.
> 
> When the BE first fires up, the HDPs won't be there, so you know it is a
> fresh install.  The user never sees these properties and wont know they are
> there.  Use them in conjunction with an encrypted MDE to log events etc.
> 
> 
> 
> Max