You would have to store the accountname in a field in the Staff table.
Then you can get the staff name, store it in a field and use a relationship to the accountmane field in the Staff table to get the StaffId.
Thanks for that - so we're actually in this case joining on fields which are names, rather than ID's?
In this case we would be relating two name fields together.
Not an ideal situation but those accountnames are not going to change really quick I guess, so this shouldn't be a problem.
Yea, the names won't change too often.
One thing I have noticed, when USER A logs in on PC 1, Get(AccountName) = USER A and Staff::Name = USER A.
When the next person logs in as USER B Get(AccountName) = USER A and USER B respectively, so both are correct, but the staff name for both has changed to USER B.
I want to avoid that if possible.
Home::LoginUser (text) >---<Staff::Get(AccountName)
The home layout has multiple records for all staff but only wants to show the most recently logged in record to all staff.
You should have a login script that sets the Get (AccountName) in a field. This field should be set to global storage.
Then this field should be related to the Account Name Field in the Staff table which is a text field where the account name of that user has been entered manually.
Through this relationship you can get the Staff Id.
Setting a field to global storage makes it so that that field has the same value on every record and it also makes it so that the value can be different for every user.