kschuster8 Posted September 11, 2006 Share Posted September 11, 2006 (edited) I'm trying to figure if I can use variables or should use a global field. I'm in a multi user enviorment. What is the best way to maintain say a users account number through their entire session. Edited September 11, 2006 by Guest Link to comment Share on other sites More sharing options...
Genx Posted September 11, 2006 Share Posted September 11, 2006 Either, Or. Advantages of Global Var: Less Trouble Quicker to initially implement Advantages of Global Fields: Will work over multiple files unlike global variables which are limited within the current file. Link to comment Share on other sites More sharing options...
ThatOneGuy Posted September 12, 2006 Share Posted September 12, 2006 ... and tacking onto Genx's Advantages of Global Fields, they can be used on the parent side of relationships. So, if you wanted to filter records based on a given user's account number, you'd need Global Fields to drive those relationships. Link to comment Share on other sites More sharing options...
Genx Posted September 12, 2006 Share Posted September 12, 2006 OH right, forgot that on Link to comment Share on other sites More sharing options...
Ender Posted September 12, 2006 Share Posted September 12, 2006 My take is that variables are best for things that are temporary, and need only be remembered for the duration of a script or a process. Globally stored fields are best for things that need to be remembered for the duration of the session, or for things that must be shown on screen, used as a relationship filter, or used for indirect record editing. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 6527 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now