I have created a DB and am able to protect the executable with a 3rd party product, but I can't protect the .usr file. Anyone with FM7 can run the .usr file and bypass the executable. Is there any way around this. I could put in a password, but that is a pain for the user. Plus how would I expire after 15 days? Would I need to give them a new password that doesn't expire? Why did they do this?

Thanks for your help on this.

You should set up users and passwords in your solution. The passwords don't have to expire. Of course you don't give your Developer or Admin password! No users will be able to go into layout mode, etc.!

But the problem is they can still run the program even if they can't execute the executable file FM creates. I am not worried about them getting into the layouts and scripts since they are password protected. I just don't want them running the program by opening the .usr file with FMP7.

I don't want to set this up so the user has to enter a password everytime. since I have the executable protected I thought that would pass through to the actual database and it doesn't. This is sorta puzzling why FM would do this. The executable is really just a way for a non FM user to launch the program, but someone with FM can just run the .usr file and bypass the executable all together and there is no affect on the database and the layouts.

Create startup scripts in each of the sub-files that are performed on startup (Edit: Document Preferences). Each of these startup scripts runs the startup script in your main file to do whatever password checking and copy protection you desire.

Steve

Steve, Thanks, but I don't follow you. The only protection I have on the files are the admin password and the main executable file that is protected with a 3rd party protection software. I want to lock people out who have FM and can run the .usr file without executing the FM executable creates to run the program. There is only one database and that has the .usr extension.