I couldn't figure this one out so....

We have several databases I'd like to relate to each other...however to open them all up at once (like you can do with the filemaker 8 business productivity system) I have to have file options set for logon with 'admin', otherwise the client will have to logon to each DB as it opens with the 'open' script.

This is fine however we have certain portals which record the name of the client (such as in notes, etc.) automatically.

Is there a way to grab the name of the logon name the client used to login to the main database for use in the others databases?

Wow sorry that was so long!

You could set a text field with global storage on login and check that.

However, you would do well to design this security better. It's a poor practice to have those files automatically login with "admin", especially if that account has Full Access. Each file should have the accounts set up in it. If the account and passwords are the same from file-to-file, users won't be prompted to login to each one; just the first one.

I agree...all our individual databases right now feature complete usernames, passwords and privileges.

I don't want to use 'admin' but I have no clue how to have all the files integrated but only use the clients logon/password for all of the databases (I'd rather not have them type in their username and password five times because that is just time consuming especially if they won't be using the other files that day, etc.)

I'd suggest you keep trying. Accounts and passwords do propogate if they are all set up correctly and the files have the auto-login option disabled.

If you want to maintain your current set up, you can have all the databases have the same password for the user. For example, Joe Small has a pasword "123joe", set up the same for all the 5 files so that when he logs in one of the files, Filemaker will transfer this password to the other files on condition that the account name in file 1 and all the other files are the same for this user and password are also the same for this particular user. Thus, you will have to set up Joe Small one time in all the five files. Then repeat for all your other users. It is time consuming especially for maintenace but it does work.

This can also be scripted using the new account management script steps. It's fairly complex, but if you have a lot of users and you want to give them control over their passwords (a good thing,) it's worth looking into.

Thanks! We have that set already where each DB has their own username and password (since we are one section and access all the databases). Is this a script set (during open) to tell the other DBs that the user already logged in and use the logon information they just provided?

what I have been doing was not using the filemaker log in log out system but I created layouts with popup message boxes that contain two globals, one for username and one for password then a log in script. I also set a guest account with no password then the script has a loop function if the username = guest. I can'T remember why I did this, but there was a reason... I think maybe when someone loged out, it needed a username to replace the current loged in person... so then it taked them to a log in page and waits. What is good about doing it through scripts is that if you have a lot of sorts and open script steps, they would have already been performed making log in very fast. Our system has many users logging in and out all the time. That is something to think about.