IWP bug or do I misunderstand "global" storage?

[joebwan]

I've been having some weird behavior with filemaker running a database and publishing it through IWP. At least I thought it was wierd behavior because sometimes a field marked with "global" storage would hold different values depending on which client (IWP or Filemaker Network) was being used to access the database.

If I understand global storage fields correctly, if one client updates the global field, all other clients should see that updated value. In other words, global fields aren't just temporary storage fields local only to the client, although they are often used that way. Is this understanding correct?

[Steve T.]

Hi, j! I don't know for sure, but my understanding was that globals are user-specific in versions up to 6. When I want global values for all users, I have to enter the global values on the host... if I enter values as a client, the globals only work for that session. I think globals may have changed somewhat for 7 to help with better web-use of globals, but again, I don't know anything for sure.

--ST

[Justin Grewe]

Yes, thats my current understanding. In previous versions of FMP, with IWP if one used globals they were in trouble because the global would be used for everyone at the same time. If one person entered something into the global, and if someone else on another machine entered something into that same global, there would be problems. Now with FMP 7, using IWP, users can have their own global and there will be no problems over the web.