Global fields problem

[idillon]

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?

[Reed]

I set up something like this in an IWP database where the data input screen was only global fields. I was getting record locking issues when I had only one record in the data input globals table.

My solution was to create several records (one for as many simultaneous sessions as I ever expected to have ~40 in my case) and have the user loop through them in the startup script and open each one in turn until no error was returned in the script. You have to Set Error Capture [On] to avoid any dialogs.

Dana

[Vaughan]

There should be no record locking issues when editing global fields.

You could use global valiables instead.

[Reed]

There are no locking problems if the clients are using FMP, but there are if they are on IWP.

[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.

[Vaughan]

Oh I see, yes.

Could it be a permissions/privileges thing?

[Reed]

Another option you could consider, if all of your users have FMP accounts, is a user table where each user has a record associated with their username. The users would be directed to their record on login. Then there won't be any record locking issues with your global entry fields unless you also allow guest access.