Prevent records being viewed on a different file.

[FossilFM]

I've got a solution that I am working on the security issues with. One thing that I did notice is that within my solution field level access works as I expect it to be but then I tried creating a test file not part of the solution files and creating a table occurance in the test file of one of the solution tables and I was able to see all the data,

I know this was covered in DevCon but i just can't remember how it was done to prevent users from seeing the data in the event that they created a table occurance of one of my tables in a dummy file.

Any tips on how to prevent this would be appreciated...

Thanks.

[Vaughan]

Passwords.

[FossilFM]

They have a user level account and password with the solution file and they can open the database file remotely with their user level account and password and still able create the table occurance in a different file. I would like it that the table occurances be restricted only within my solution files.

Is this possible?

[Vaughan]

There are others with more FMP Security knowledge than I, but I cannot see how to limit that.

If the user has a password they can see the records, regardless of the file it's through.

This may throw up weaknesses in "custom" security features that involve relying on scripts or layouts restricting access. By themselves they cannot. Real security comes from configuring the passwords and access privileges appropriately.