I have 2 related databases ‘Jobs’ and ‘BA’. Both have the same privilege sets and users.

‘Jobs’ asks for login credentials when launched and opens into the ‘home’ layout.

‘BA’ opens into a small layout/window called ‘Login’ that only displays a couple of buttons. If either is clicked, Relogin is the first step in the script.

Users are asked to log out whenever not using either db. Clicking the ‘Logout’ button in either db, they are taken to a small ‘Login’ window and the ‘Logout’ script uses ‘Relogin without dialogue’ to put them in an account called ‘Logout’.

The ‘Logout’ account has its own privilege set with very few privileges.

Now the problem – when the user runs a new enquiry script in ‘Jobs’, one of the steps is SetField on a matched field in ‘BA’ (used in a lookup relationship). Even if the user is admin, he gets a ‘no access’ warning, when ‘BA’ is in the ‘Login’ window (and, therefore, the ‘Logout’ account).

The new enquiry script is running with full access privileges and I have given the ‘BA>Logout’ account full access to the BA>Lookup layout/record/matchfield, but this hasn’t fixed the problem.

Presumably anyone accessing a related database is restricted by the current logged in account on that database, but what else can I do to give access to the running script?

Perhaps your script in the Jobs file should call a sub-script in the BA file - and have the sub-script set that field.

And perhaps you are making this too complicated and could do with both tables being in the same file.

I'd love to have both tables in the same file. Unfortunately, part of the data will be taken off site on more than one laptop and then synched with HQ on it's return. Locations are frequently off wifi and mobile phone networks. The db has been created in 3 parts to reduce the amount of data synchronisation.

After what seems like hours carrying out a process of elimination and testing, in the security features, my problem turned out to be too severe a lock down.

I had locked the account down to access only the field it needs access to (used by the new enquiry script that was causing hassle). As soon as I gave the account access to all fields in that layout, the problem went away (even though the script doesn't access any other field).

Thanks for your thoughts.