Global field in a single record file

[ibiubu]

I was setting up a file to act as a pref. file for the rest of my related database files. you know, general company info, company logo, ect that then will get used by the other files. I had read somewhere that if I would set up this pref file as a single record file on the host computer I could use global fields that, if modified by different users, would change the data in the global fields on a permanent basis.

I tried this but it does not seem to be the case. If one user makes a change from a client machine to the hosted pref file to a global field, the change does not stay if another user later looks at the same file. I understand this is the nature of global fields, but I had thought that if it was a single record database this would resolve this.

Am I mistaken in this assumption. Does this mean that the only way the prefs file containing the global fields can be edited is on the host computer itself and not thru any client computers?

LR

[falkaholic]

If its only ever going to be 1 record just use fields in a record. There is no reason to use globals if you know its only a single record DB. Globals have some draw backs, like how they are treated in multi-user systems and they can't be in indexed calculations.

[BobWeaver]

Globals are globals whether they are in a single record file or not. Each user will have his/her own set of values.

The advice about using a single record file is to use normal fields, not globals. Then, the values in the fields will apply to all users.

[ibiubu]

That is kind of what I was thinking. I must have read it wrong. I figured they should be text fields, not globals.

Switching the fields over to golbals seems to have done the trick.

Thanks