Protecting Full Access Passwd on Unsecured Machine

[m sloper]

I have a .fm7 solution which is sold to offices where i don't have security control over the filemaker host. Without this physical security of the machine, the database seems pretty open to mischievous password crackers. I am worried that a particular office has cracked the Full Access password and has been programming the database w/o me.

Anyone have any good ideas for making sure the Full Access privilege password hasn't been changed?

[T-Square]

The only way I have heard to address this is to strip Full Access from the file, which won't help you much, since your (ex?) clients already have a cracked file. Perhaps you can fool them into loading a newer (stripped) file?

David

[Steven H. Blackwell]

Do use the Developer Tool to remove the [Full Access] accounts remembring that you must give the users the ability to retrieve their data.

Second, be sure to include a statement on the splash screen that the solution is licensed to the group and that reverse engineering in prohibited.

Steven

[m sloper]

I want code that could be used for all my clients and some of these clients buy support from me, so I don't really want to disable the Full Access user.

I am thinking about using some sort of notification alert. Everytime access privilige = full access, send an email (SMTPit) or make a post. At the same time, secretly sending out emails rubs me the wrong way.

Any other ideas?

[m sloper]

Thinking this over some more, for my customers that don't buy support from me, removing Full Access user does seem like a good idea. Thanks for your help.

[Steven H. Blackwell]

Why limit it to just those who don't buy suport?

Steven