Jump to content

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

Recommended Posts

Is there a way to prevent a user from accessing your scripts?

For example, can you distribute the FP7 file and use security to allow them to run the application but not modify it? Change scripts, layouts, etc.?

Link to post
Share on other sites

Have you already tried Manage>Accounts and privileges? If you are the full access user with password, then creating a read-only or data-entry only or whatever level of access you want to provide should do the trick. There are tons options if you edit the privilege set.

Link to post
Share on other sites

However...(and some with more knowledge that I can chime in), if your solution has an active Admin account there are several "Crackers" on the market that can let someone gain access to your solution.

I purchased one just see how easy it would be to gain access to the admin account of a project I had started. It was basically as easy as entering a new Admin password in a box and press an open button (I think they may do some damage the file, but you can get in).

I think the only truly safe application is a Runtime with the Admin completely removed.

That is why I use nothing but Runtimes and use the updater solution by bcooney.

Jim

Link to post
Share on other sites

Yes, it was just that my point was the only secure solution you can distribute is a Runtime, all others can be cracked.

I will have to find the link, but bcooney (who posts here) provided me with her update solution for Runtimes which has worked out great for the Runtime solutions we push out.

Jim

Link to post
Share on other sites
  • 4 weeks later...

You can script turning on multi-user access. I purchases an app the was distributed as run Time files. As single user you could run with runtime. To run as multi-user you used with full copies of Filemaker, just opening the run-time data files. worked great.

Link to post
Share on other sites
  • 5 weeks later...
  • Newbies

Filemaker Advanced has the option of removing the admin accounts using the runtime creator. It has been a while but I believe you do not have to create a runtime to do this, just remove the admin accounts and access.

Since you would set up other accounts with various priviliges, or just one with selected priviliges, your users can run the file but not have access to scripts, layouts etc.

Link to post
Share on other sites

This topic is 3634 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
  • Who Viewed the Topic

    1 member has viewed this topic:
    Wilton 

×
×
  • Create New...

Important Information

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