This is probably a simple one, but I am having trouble implementing it.

I have a database that will have a number of clients accessing it on the web. These clients will login, and only access records belonging to them - in my case, the login name with be used is a client field and thats all they can access.

If at any time they "Show All Records" they will see the records of other clients as well. Whats the best way to get around this.

I was thinking of having a client-x.fp7 for each client so they only see what is in their file prefer to work in a single file only - instead of multiple.

How can I prevent them seeing all records other than their own please?

Greg

If at any time they "Show All Records" they will see the records of other clients as well. Whats the best way to get around this.

Firstly, you need to use Filemakers accounts and privileges to explicitly restrict access to the records (don't just rely on scripts as these can potentially be circumnavigated). For example, you could set a privilege set that matches the 'user company' field (this could be a global set at login based on their account details) with the 'data company' field and only allows those records to be viewed. Then, any records that do not match those criteria will display "<>" in all the fields.

Next, you will want to script any functions like 'Show All Records' or 'Perform Find' to restrict any found records to those that match the above criteria. This way you can prevent the user from having to navigate through multiple "<>" records to find the ones they want to see.

Does this give you a starting point?

Thanks tv_kid

I will look closely at the explicit record access.

Cheers,

Greg