[AccessD] Copy Protection Needed

I hate software that utilizes a hardware derived key. What happens if the
developer goes out of business? When it comes time to install that new hard
drive or simply reformat and start over again you'll be out of luck. I know
this is much more likely with smaller companies but it has happened. 

I know it's not as secure to use a registration information based key system
(User & Company Information), but it is much safer for your customers (and
you for the software you use)... ;-)

WBR
Robert




-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, May 01, 2009 10:47 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Copy Protection Needed

I'm kind of with John on this one -- I'll man those phones! ;)

In my delirium I came up with two possible copy-protection ideas, and I'd 
like to hear pros and cons:

1.) Create a key in the registry with a simple Boolean value, when the 
application is first launched. Then the program is launched, checked for the

key -- if it's there, proceed. If not, lock things up with the appropriate 
warning and contact information. If it's good enough for MS, it's good 
enough for me. This is a relatively simple process to implement.

2.) It seems to me that there ought to be a way to manipulate the GUID data 
type with some internal system value to create a one-time key value that 
won't change, as long as it's on the same system. If that's possible, simply

compare that value each time and respond appropriately. I don't know if this

is possible.

Thoughts?
Susan H.

SNIP