It 's hard to determine what you have done from the description, but I think you are using fields with global storage specified.
When a file is hosted over a network, changes made to a global variable are not visible to other users and the value in the field reverts to it's original value when the user closes the file
If this is why you are having this issue, you'll need to modify your design such that either all users get the same value in the global field when they first open the file via a script or to replace the global fields with non-global fields.
Thanks for getting back to me! I think you're right..So basically, if I want a value in a field to say ie: ''hello'' and that it stays that way to then use it to filter all that says ''hello'' , I do not need to make it a global storage?
I just put a fixed value of ''hello'' and that's it? I can then link it so that it filters the value list based on the field ''hello with it not being a global storage.
Thanks again for your time.
If the value will never change, I'd use a calculation field with
as it's calculation expression.
If it's possible that the value may need to be changed from time to time. I'd use a global field, but I'd have a start up script "load" the global field from a value stored in a non-global field each time the file is opened.
Thank you very much