Copy-Protecting Run-Time Solutions

[mberding]

So I've been doing a little research, and it looks like run-time solutions can't open databases stored on FM Server.

So, how can I prevent my runtime solution from being pirated left and right? Are there any standard procedures for this?

[QuinTech]

Hi, Michael. One thing you might do is find something that must be unique for the user, such as a phone number, and then make a password based on it that is unpredictable for most users. The user would have to call you for the password. If he has entered the wrong password, he cannot get past the login screen.

Maybe phone number is not the best bit of data for you to use. You should select something that would incur a "penalty" if the user did not use his own information. The phone number example would be applicable in cases where the user needs a printable form with his phone number on it, and having somebody else's phone number would be inappropriate

[RalphL]

If your user has FM Server, why would you want to supply them with a runtime?

I would make the runtime very customer detailed. Name, address, phone number on every layout, making it useless to anyone else. I would use the the developer tool to remove the full access privileges from the database.

[pjdodd]

You could include a startup script that occurs ONLY on the first launch that requries a password etc....entering the password could deactivate a check to see if a first launch has occured. Additionally you could add/create/copy a file to a hidden location on that computer whose prescence and/or content is checked on every startup....might help prevent theft.

Also, remove admin access as suggested.