Hello Wally

I did do both of them, the problem with numbers of records is that I have 3 years of historical data i.e. over 200,000 records.


>Stephen,
>
>I was in the same boat as you, I wanted something that they couldn't use forever, a coding solution also that didn't cost me anything.
>
>I chose to simply let the users build up a certain number of records in certain key tables and then after one of them goes over that limit, I consider it to have maxed out the demo version's usage and I shut it all down. Every time they try to save after they go past the max it just tells them that it is the demo version instead of saving. So, I figure they can't run their businesses for very long with the demo before there will be too many records in one of those key tables. Then once they cross that threshold it is over.
>
>I thought about doing a time sensitive thing, but the users can always and perpetually change the dates on their computers if I did that. And the other problem with time sensitive things is that a lot of them are very very slow about thuroughly reviewing the demo version to check it out. But some marketing people would argue that you want it time sensitive to force them to look at it and make a decision in a certaintime frame.
>
>Wally