I'm working on a database in which different users can fill in their hours. They should only have access to their own records. I know I can make different passwords and groups to organize this (I did it and it worked) but when the users change, I have to change the access privileges into each database (a lot of relations). Is there an easy way to arrange access privileges without a lot of editing. I tried 'gateway' but I can't get really into the program. (I can open it and see that it works, but I can't see how)

Hello Hans,

If users only need to log their times, then I suggest that you consider giving them access via a portal in a specially built interface file.

The interface file should have a relationship to a user list file so it can prompt the user to enter a username and password, check if the details entered are accurate, and if they are, it should place the userID into a global field.

Then, if you define that global field as the key field for a relationship to your other files, users will be able to access their own record (via the relationship) once they have successfully logged in via your username and password system, but they will not be able to see anything else - and there will be no data in the file they are working from so there will be no chance of them stumbling onto a different record.

A log-out script need only clear the global field, thus breaking the connection until a user runs the log-in script again.

Finally, to complete the process, you will need to lock down and hide any other databases so that they are safe from prying eyes. For instance, you could ensure that the FM passwords that the other files are open with only provide access to a single blank layout, and your open script could hide and lock the status area in all the files and then hide the files from view. If you have access to plug-ins such as SecureFM, WindowUtility or MenuControl, even greater security is possible.

Thanks Ray. This helps me a lot. Really simple but offering a lot of new possibilities.

Hans