Hi all,

I'm sure I've read something about my question in this forum but now I'm not able to find it.

I've a project database with a master/detail interface, i.e. each project has a portal showing the project's jobs and the details for a selected job.

There are two possibilities to save the current job selection: 1. save it in a (non-global) field for each project record, 2. save it in a global, database-wide field. The problem with the second approach is that the currently selected job shown in the detail view may be not related to the current project record (since the selection is not tied to the project but to the whole file). The problem with the first approach is that it's not multi-user compatible.

Now the question: Is there any way to implement some sort of complex, record-level user preferences, preferably in an extra file? I've some difficulties to find a solution.

Thanks

-- erik

Data cannot be "saved" reliably into a global field. It may work in single user mode, but once shared in FMS or used multiuser, global fields hold values only for the duration of the current session independently for each user.

The solution is to make a user prefs table (or file) and store the data in that.