Jump to content

Restrict runtime solution to one computer


Daniel Shanahan
 Share

This topic is 4395 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Can a runtime solution be restricted to one computer?

There are a couple of different ways you can attack this.

Have either a global field or a single field in a prefs table (1 record table) to hold the data "Value". Make sure that it is empty the first time the client runs the program. Have another field for comparison "Check".

Then in your startup script:

1. Check to see if "Value" is empty.

2. If it is, you can use either Get(AccountName) or Get(SystemNICAddress) to set an initial value. One will give the current account on the computer and the other should give the current NIC address of the machine ethernet card (have not played with this one). One validates down to the individual user and one validates to the individual machine.

3. On subsequent runs, "Value" will not be empty, so, have the program set "Check" with either of the parameters above and then compare "Check" and "Value" to see if something has changed.

Link to comment
Share on other sites

This topic is 4395 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.