[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.

----- Original Message ----- 
From: "jwcolby" <jwcolby at colbyconsulting.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Sunday, April 26, 2009 8:08 PM
Subject: Re: [AccessD] Copy Protection Needed


> >The consequence of which is that the customer has to contact direct by 
> >email or phone with a
> hardware-related 'Fingerprint number' on first installation, and you have 
> to run a utility and email
> back their unlock key.  Which obviously would be a drag if you are talking 
> high volume sales.
>
> ROTFL.  Answering an email to provide a key to obtain a $400 sale is a 
> PITA?  Hmmm...  I'll do it
> for 50%.
>
> John W. Colby
> www.ColbyConsulting.com
>
>
> Steve Schapel wrote:
>> Ricky,
>>
>> For several years I have been using Sagekey Security 
>> http://www.sagekey.com/security.aspx
>>
>> Of course, you have the expense of a licence from Sagekey.  But in my 
>> opinion it's well worth it.
>>
>> There is a web component, but I don't bother with that.  The consequence 
>> of which is that the customer has to contact direct by email or phone 
>> with a hardware-related 'Fingerprint number' on first installation, and 
>> you have to run a utility and email back their unlock key.  Which 
>> obviously would be a drag if you are talking high volume sales.  But for 
>> a moderate number of end users, it's not too burdensome, and always works 
>> like a charm.
>>
>> Regards
>> Steve
>>
>>   From: Rocky Smolin
>>   Sent: Sunday, April 26, 2009 3:59 AM
>>   To: 'Access Developers discussion and problem solving'
>>   Subject: [AccessD] Copy Protection Needed
>>
>>
>>   Dear List:
>>
>>   Susan Harkins and I are working on a project together  It is a 
>> relatively
>>   small application and database for the Toys for Tots organization - 
>> tracking
>>   parents, children, donors, and volunteers.  We were contacted by the 
>> head of
>>   a Michigan chapter after he had gotten bids from $2500 to $10,000 for a
>>   custom database - well out of his budget range.  So we decided to put
>>   together an application for him, speculating that perhaps other Toys 
>> for
>>   Tots chapters around the country would find the application valuable. 
>> He's
>>   up and running and very happy, has provided us with a nice endorsement, 
>> and
>>   will post a notice to the TFT bulletin board for us when we get a web 
>> page
>>   up.  Which should be in a couple weeks.  We have priced the product at 
>> $400.
>>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com