Drew Wutka
DWUTKA at marlow.com
Mon Jun 9 18:48:36 CDT 2003
An automated reg key system will let you users get a new key whenever they want. It's one additional step when installing software on a new or replacement machine. However, it should make them think twice about copying the software, because you are logging the keys that are requested. It would be up to you to look for suspicious users. Drew -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Monday, June 09, 2003 6:07 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Registration routine for a commercially-sold Accessapp? That assumes the app won't get moved between machines. We've had to give out new keys for replacement installations for laptops that were fried by lightening or that fell off drilling platforms into the ocean! Charlotte Foust -----Original Message----- From: Jim Dettman [mailto:jimdettman at earthlink.net] Sent: Monday, June 09, 2003 12:52 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Registration routine for a commercially-sold Accessapp? I would second that. It's unique world wide and fairly stable (NIC cards don't get changed all that often). I've got code for it if anyone needs it. Just send me and e-mail off-list. Jim Dettman President, Online Computer Services of WNY, Inc. (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Drew Wutka Sent: Monday, June 09, 2003 3:56 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Registration routine for a commercially-sold Access app? If you roll your own, I would go off of the MAC Address. That's unique, and easy to retrieve. Drew -----Original Message----- From: Christopher Hawkins [mailto:clh at christopherhawkins.com] Sent: Monday, June 09, 2003 2:13 PM To: accessd at databaseadvisors.com Subject: [AccessD] Registration routine for a commercially-sold Access app? I need to come up with a registration/licensing routine for an Access app that a client of mine will be selling. Basically, my client is concerned about one customer distributing the application to others. I want to roll my own algorithm, but then it occurred to me there might be a better way. Right now I'm experimenting with validating the app against the hard drive serial number, but that's fraught with shortcomings. I'm also thinking about using an obscure registry key. Who's had to come up registration methods before, and how did you do it? -Christopher- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com