Hi there,

Just wondering other than using a field that uses Global Storage, is there a way to create a dedicated variable to each user?

For example user 1 his variable is 10

User 2 does something and his variable is 12..

Variable that entirely depends on what that person does.

I know one way to do this is to create a field with global storage...

Your question is not clear. You can declare variables using the Set Variable[] script step as well as during a calculation. These variables are user-specific (or rather session specific).

If you tell us why you feel you need the technique, what you're trying to achieve, we can provide better answers and help you avoid painting yourself into a corner.

Some people use the term "variable" when they mean "field," is that the case here?

If the idea is to have user data that persists between sessions, create a user table.

Assuming you have 2 users using the database at the same time..

I have a set variable maybe say $name using custom dialog when they login wanting them to type that in.

So 2 users were to use it at the same time, i mean type the same type, will the variable be dedicated to the each user?

So far i have been doing that using Global storage for the field..

Example Case :

User A Types James into $$name

At the same Time User B types Johnny into $$name too since they use the database at the same time.

What will the outcome be when i set a field to $$name? Will it show James for User A and Johnny for User B?

Thats what i want.. Dedicated for each user that is online.

User A Types James into $$name

Unfortunately, it's not possible for a user to populate a variable directly by typing in a custom dialog. But - as I said - variables are user-specific, so there will be no conflict if two users have a variable with the same name but different content.

using custom dialog when they login

I am not sure what that means. If you're trying to replace Filemaker's login process with your own, I'd advice against that.

thats great to hear... Global Storage for a field works fine too..

Hmm i was just thinking of ways to block passware form doing its job... @_@

I'm not sure what (if any) those ways are, but I'd suggest caution:

http://fmforums.com/forum/topic/46502-known-vulnerabilities/