Go with a number of runs limit rather than a date. Release the app and with 50 trial uses. That way if they install it and forget about it until after the 30 days they can still try your program. Write the number of uses to a file in the registry each time using the API (you will have to convert your api function declarations to mapbasic variable structure but that is easy) name your file something that sounds system critical and give it a .dll extension to fool even the most experienced users. Each time the program runs have it check the number written to the file and add one to it if it's greater than fifty Note "Your number of trial uses has expired." Exit sub.
-----Original Message----- From: Frank Aaron (EUS) [mailto:[EMAIL PROTECTED]] Sent: Friday, January 10, 2003 8:50 AM To: '[EMAIL PROTECTED]' Subject: MI-L MapBasic Question I produce a number of mbx's that are employed by our company's internal employees and external contractors -- to that end would it be possible (and does MapBasic support) to integrate a segment of code that would limit the duration of the program's usage? Currently, we have several Visual Basic Applications where a code segment and a licensing program allows us to set the applications duration of use and protects against roll-back of the PC's clock. Does anyone have recommendations or examples of how one might be able to add such functionality to a MapInfo/MapBasic Tool? Thanks in advance, Frank Aaron --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 4847
