"... you mean these fans?" Posted March 1, 2013 Posted March 1, 2013 Hi, Question ... I know you have to commit the record when using "SET ..." but what if I'm setting global fields on a layout ? Do I still need to "Commit the Record" since there really is no record yet?? in my script step ?? Also, can multiple users be on the same global fields, log in from different computers ... as with a regular field if someone is in the fields nobody can enter any data until the user is done, is this correct ?? Older version vs New version. Thank you.
webko Posted March 1, 2013 Posted March 1, 2013 There's no harm in committing the record - if it's part of a find script then it will have no effect... But for the second part... a field defined as global has values on a per user basis. The next user has the same fields but with their values... and so on. When they login, the global fields will have a default value. But this may change as they use functionality. Let say you have a field gUserName which is a text field global. It's default is "" - a blank field. After logging in, you may set this as part of the login process to their Account Name - "Tim Booth" - and this can be used to say find only records that belong to that account. When you login, it may be set to "Snozzles" and then could be used so you only find records belonging to you. But the value for me is separate and different to yours, as is the field itself. No table locking on that field... 1
Recommended Posts
This topic is 4340 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