Hey, there is always a way to hack. It just depends on how much effort someone will go through to break the law. Hiding the information in an INI file might be an idea. Like WIN.INI or whatever. Of course that can be found too.

How about this: Add a decoy file with an obvious name that a hacker will quickly spot. But, also add a line in an INI file that holds the same information. Make it quite clear that the software is time-limited and it is illegal to use it past the amount of time allowed. Smart-guy hacker finds the obvious file and deletes it and chuckles to your warning. Breaking the law is a rush. Your install program see that the required line is in the INI file and decides to format the c: drive.

Hey, trust is a two-way road.

Joe


>I have worked on this one for years and the problem with changing or updating files on the system is that the user can sort all of the files by time and date and then always check for the most recent updated file in the directory or on the drive and then find the file that you are updating to control access. I also believe that time limited demos are more difficult to stop people from cheating than by limiting the number of records. You could then control the number of records in the code it is much easier that way and then you could send the customer a digital certificate stamped to their data to unlock the 50 record limitation. You will also want to use something like REFOX with Level II encryption to send out your product as well. Otherwise, nothing is safe from those in the know. Remember kids are learning to hack at Age 5 now. They're getting a lot more practice these days.