Hi, I am working on a solution that will be shared by 9 users. I created one table called Users. Each record in this table will handle all temporary data, like layout name, IDs from other tables, etc. Next, I set up relationships to all other tables to filter information or to create records. This way every user will have his/her own "globals".

My problem is that I don't have a network to test what I am doing and this is my first shared solution.

So I don't know if it is better to use Global Fields or to do what I am doing at this moment.

Thanks for any feedback

As long as no two users will have access to the same records, you should be okay. I think it would probably be easier, however, to just use one record and make all the fields global. It depends whether you want to have the data stored for the next session when a user closes the solution. Non-calculated globals reset themselves to their default values (values assigned the last time the file was opened in single-user mode) when FM opens, whereas your normal fields would retain their data.

Somewhere I read or heard that when you create a multiuser solution you should not use globals (please don't ask me why). This is the reason to create one record per user accessing the solution.

It is very important that every user can access related information throug relationships.

I have the User's TO and, various relationwhips connected to it.

I just want to be sure that each user has one place to store temporary informtion, and that the information is unique for everyone

In a multi user envoirnment global fields are unique to each user. They will have an initial value that is common to all. They are not remembered from one sesion to the next.

You use a one record table of normal fields to store values that are common to all.