Restrict runtime solution to one computer

[Daniel Shanahan]

Can a runtime solution be restricted to one computer?

[David McQueen]

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.

[Daniel Shanahan]

Thanks, David. I'll give that a try.