idillon

Thanks for the replies. It's a shame the record locking only occurs in IWP as that is how I want all clients to access the database. I think I'll use several records as suggested with one field recording the client's account name. Rather than keeping 40 records I'll create a new record for each session and delete it at the end of the session.

I don't know about your erasure problem but have you checked the layout you can't type anything in to? Are the field behaviors set to allow you to enter those fields in browse mode? What about find mode? Also, have you checked the permissions for the layout to see if your account has read-only access to its content?

I've read that the values in global fields in a table are different for each user session. However it seems you can't use just one record in a table to store all those different values because I've encountered record locks when two users try to access a global field at the same time. Is the only way around this to create a temporary record for each user session?

When you create a file reference to another FM file you can access value lists from the other file. However, you don't get the option of showing a different field instead of the index field (i.e. a field that means something to the user). I know that I can include the table from the other file in the relationships graph and then create a value list from it. Then I can make the second field appear. Is there something I'm doing wrong with accessing the value list directly instead of having the table in the relationships graph?

I've set my IWP to show the status bar (the one on the left) when I login as Admin but its hidden for everyone else. When I move from one layout to another via a script and use go to field to bring the focus to a particular tab with the field on it, I end up with the choice of cancel or submit in the status bar and the value from the first record for the underlying table showing in the field the script took me to, no matter what record I am actually in. If I click submit the value from the first record (for the field the script took me to) overwrites the correct value but leaves the rest of the values in that record untouched! Users who can't see the status bar don't experience any problem. Is this a known bug?