For IIS demos, I'd suggest a COM object, that has access to the registry, as well as sets an application or session variable. If that variable doesn't exist, the object wasn't called or initialized. (Very crude example, implementation would be somewhat more complex).

The problem with ASP is that no files are compiled (except on the fly when run through the ASP engine), so no matter what you put in your files, the user can go in and change them manually.

Hugo

>Dear Friends
>
>This sounds very good. I stored the Demo Installation date in 2 places in Registry in encoded form. What I am facing problem is with the internationalization. Say if I install the Package on Norway machine then I am facing the problem in retrieving the Date. Also I do not have permission on Registry as my demo uses ASP over IIS, if I install the demo on IIS Server. Is there any way other than this method that can be used for trial checking.
>
>
>>Hi Craig,
>>
>>I checked out your KB article because I was curious as to how other people implement this. I generally use the date scheme myself (give them 30 days, and also give them a way to extend it if they call me --- I give them a 15-digit code over the phone to enter to either extend the demo period or remove it once they've paid me). The only objection you seemed to have was that there was no way to prevent them from changing the system date. You're right about that, but what I do is save the current date each time the program is run. When you do your security checks when the program first starts, you can check if the system date is less than this saved date. If so, you know someone screwed around with the system date and then I immediately expire their demo. Once it's expired, they have to call me to get it back.
>>
>>-Bonnie
>>
>>>>This is a general Query......
>>>>
>>>>I am creating a Product etc. and I want to have a Full Version and Trial Version Softwares. What are the Industry Standard Practices followed ? Are there any other methods ?
>>>>
>>>>Thanks in advance
>>>>
>>>>Satya
>>>
>>>Look at the KB article on my web site.