RobinHood786
Technical User
Hi all,
I’m going to be distributing a demo version of an app, which I want to allow users to run unrestricted for 6 months, after which time I want to either allow usage with restricted functionality or simply display a messagebox then exit. (Not quite decided on which way to go)
I was wondering how others implemented such restrictions. My initial thoughts are to simply compare the current date with a date in a table and if the current date matches or is greater then the table date have a Boolean field in the same table set to true. Then, perhaps on the load event of the startup form, test for the value of the Boolean. If true trigger a message before exiting, or apply restrictions on usage, although I’m not sure yet how I’d go about doing the restrictions thing (perhaps testing for the value of the same Boolean again before allowing execution of code would do the trick).
Any thoughts, ideas or a heads-up for gotchyas, will be gratefully received.
I’m going to be distributing a demo version of an app, which I want to allow users to run unrestricted for 6 months, after which time I want to either allow usage with restricted functionality or simply display a messagebox then exit. (Not quite decided on which way to go)
I was wondering how others implemented such restrictions. My initial thoughts are to simply compare the current date with a date in a table and if the current date matches or is greater then the table date have a Boolean field in the same table set to true. Then, perhaps on the load event of the startup form, test for the value of the Boolean. If true trigger a message before exiting, or apply restrictions on usage, although I’m not sure yet how I’d go about doing the restrictions thing (perhaps testing for the value of the same Boolean again before allowing execution of code would do the trick).
Any thoughts, ideas or a heads-up for gotchyas, will be gratefully received.