Copy protecting a database 1

[jgoodman00]

Howdy again people,

I am interested in what people do to copy protect the databases they create. My current project will be distributed, & we are particularly concerned with it being copied. I have dreamt up the idea of taking a piece of information (say the HDD serial number, or simply the current date), & then assigning an algorithm to it. Then the user installs the software, gets to a registration screen at which point they would need to contact myself in order to get the unlock code (from the algorithm i have already decided).

This is where my thinking has led me, but I think this would be quite complicated to implement, so does anyone knwo any simpler mathods, & if not if anyone has done something like this in the past....

 

[calian]

Are you concerned with protecting the data or just the work you've done on the application?

 

[jgoodman00]

Basically we don't want anyone to be able to copy our front-end application or back-end data. It is going to be distributed to many people, & we do not want them to be able to use our database on any computer other than the one we give permission for.....