Franco,

>
>1) by default users can insert only 10 records in every tables, this is the demo mode....
>

Yes, this is an option that works for most applications. In my case this does not work
as the user cannot deeply test the application if I did that. so I have to stick with
just the time blocking.

>
>2) the second one is similar to your one's, but we refer to the "number of days" as days
>of real use the software. .... we mean the the application works for 60 different days not
>

This is an approach I really like when I test software. In most cases You download
a software and try it once. Then something important comes in between and the next time
You have time to try the software is 30 days later. So this is just day two and not day 30.

However it's still easy to betray. I can always set my system date to the 15th of July and
work with it forever, since the software - checking on every startup - "thinks" it's still
the 15th of July that has been logged already. In this case You would also need a counter
that lets say allows to start the software 10 times a day. After that it would just add
another day. Still this would allow a user to use the software on 300 days instead of 30
until it finally quits its job.

There must be better ways to do that.