Howe9999 Posted December 18, 2003 Posted December 18, 2003 I want to use a global field, repeating with a list of items I want to see with all records. If I type list on main file everything is great and works the way I want but if I change anything or add items from a remote computer it only shows up on the computer that I type it on. Then after disconnecting and reconnecting to "host" everything is gone. If there a way around this problem?
John Caballero Posted December 18, 2003 Posted December 18, 2003 Yes. The problem is that globals in a multi-user environment aren't truly global. They're global to each user's machine and only for that user's session. As you've observed, only the host machine's global values seem to work. Create another, single record file, and instead of a global field, use a regular field. Create a constant-to-constant relationship to this file from all the files that need the value.
Lee Smith Posted December 18, 2003 Posted December 18, 2003 Hi Howe, This question comes up all the time. FYI, Global fields are set before you serve the files. From than on, the become local to the user. Any changes that you make and want to reflect to the users, have to be done by taking down the files, change them, and then served again. Lee
John Caballero Posted December 18, 2003 Posted December 18, 2003 Hmmmm... What's really needed here is a User preference file of some sort. In my previous post, the value that is set in the single-record file won't be lost the way a global is in a multi-user setting, but it still won't act as a global value the way it does in a single-user setting because whatever value is set most recently would be the one the next user saw. Each user would need a record in the file.
Lee Smith Posted December 18, 2003 Posted December 18, 2003 Until the file is closed, you are absolutely right. And thanks for your help, in helping me catch Ugo
DanBrill Posted December 18, 2003 Posted December 18, 2003 I've thought that that FM 7 needs a 'Universal' field. This would be like a global, but would affect the whole database, not just one user's session. Maybe there's a workaround for this. Dan
Recommended Posts
This topic is 7715 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