When Variables were added to FM functions and scripting, I quite trying to use contents of Globals "as-is" in finds.
If you are scripting, set the value of the global(s) to variable(s) at the beginning of the script and then use the variable(s) in the rest of the script
Set Variable ( $myVAR ; globalfield )
Enter Find mode
Set field ( searchField ; $myVAR )
I understand what you are saying and have got into that practice myself elsewhere so I will make the change that you suggest. However, I don’t think that’s where the main problem lies as the problem arises before the script is triggered (i.e at the point when the user attempts to enter a value into the global field).
are you IN Find mode or Browse mode when the user populates the global field?
can you post your script?
Good morning Paul,
I hope your day is going well. I want to make sure I understand the issue you've described correctly before I offer any suggestions. Does the error message appear when the user begins to type in the field, or when they exit the field? Thanks and have a great day!
The access privileges of your users do not allow them to modify that field. Edit privilege set, Records -> custom privileges -> Select the table -> Field access -> Limited... search for your global field and allow editing it.
Thanks to everyone for responding.
The problem is entirely of my own silly making. Turns out it was a privileges issue.
I had set up the Job_list layout for "View only" and, therefore, I didn't allow the drop-down field to be changed even though my field setting access (referred to by siplus above) showed all fields in the table to be editable.
So that I don't get interference between users, I have implemented Beverly's suggestion.
Thanks again for being my sounding board. It really helps when you have to explain to someone else what the problem is .....