Global fields in a multi-user environment

i have a filemaker database running on a stand alone computer. i have 4 users accessing the database through filemaker remote. i used to have just one user and we hired 3 more in the past month. the database was stable when only one user was accessing the database. now, every so often when 1 user prints a form, the data on the form is not from the record she is choosing.
my question is: do global fields apply to the specific user logged in or is it based on the database?
can each user have  values defined for the same global field that is unique to them?
kauakeaAsked:
Who is Participating?
 
lesouefCommented:
variables are user specific.
more reliable? no, but avoids wasting fields for temp things, and more flexible since they can be global to a user ($$var), or specific to a script ($var). they are also independant of any layout unlike fields.
back to yr problem, it should not happen for sure; there must be a script error somewhere or there must be a layout where it is not found?
I suggest you display that ts_number in all layouts to try to locate the pb.
0
 
lesouefCommented:
If the file is stand alone, the global field is stored
If the file is shared and hosted by a fm server, the global field value is never stored and is local to each client. It may contain a value at file open, and this will be the last value used in stand alone mode before sharing the file and placing it on a fm server.
And finally, when sharing a file using the basic filemaker pro as you are doing, I have no idea and can't test now as I have only 1 fm client, but it's easy to check.
Change the value of the global field, and see if it changes on the screen of the other users: if yes, then the value is common to all and you're trapped, you must store the current user a different way. If you use FM8, use variables instead of global fields
0
 
kauakeaAuthor Commented:
thanks lesouef, i didnt think to test the global values.
they are user specific. each user can have a different value. i inserted the global field in question on the main layout  and each user had a different value displayed.


the reason for my question is that i have a database that has one common control field in all the tables. the field is ts-number. i also have a ts-number global field that i set whenever the user moves away from the main information screen and i use the ts-number global  to do a find so that they return to the same ts-number screen they were on when they left the main information screen.
but sometimes they do not return to the same ts-number they originally left from on the main information screen. they would return to a different ts-number. it is not consistent and is not always the case. so i am trying to determine where the problem might lie.

are variables user specific?? are they more reliable than global fields?
0
 
kauakeaAuthor Commented:
i didnt realize $$var was user specific. i thought it was database specific which is why i did not use it. i think i will change my global references to a $$var value in my scripts.
thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.