2 questions on global fields

[Baylah]

Hi,

I'm having a problem with global fields, one is a question, one is something I have never experienced before, and is counter to the way I understand global fields.

1: Is their a way to prohibit the changing of a value in a global field without "hiding it" on a layout that is not used? The prohibit modification box is grayed out in the field creation menu.

2: On a soultion I am currently using the value in a global field keeps disapearing. I set it (at 2,500, not that that matters) and then the next day it is gone. I thought that once you set a global field, that unless modified it is supposed to remain unchanged across all records, and be present whenever a new record is created. Is this correct or incorrect assumption on my part. I've use other global fields and this does not seem to happen so I don;t know what is going on.

Thanks for any tips or advice.

Steve Freeman

[Søren Dyhr]

This is a FAQ, globals vanish into thin air when finishing the session, and the value stored in it are personal, so each user have their own value to deal with. A solution is to make a record for each user to store their own value a relation away in another table as a regular non global field, other records could contain common globals. A way to make the keying work is to use Get(UserName) for the relation to the table.

--sd

[Baylah]

Thanks for the quick reply, and sorry that it has been the topic of an FAQ, I always forget to check the history as my qustions often come to me on the fly.

<<A way to make the keying work is to use Get(UserName) for the relation to the table.>>

Can you elaborate on this a little for me? In reality though, I do not want this field to be user driven, therefore should I figure out a way to HARD CODE this number into the area where it is needed?

Thanks again, you totaly answered my question though and have give me a very powerful tidbit I was not aware of to use in the future.

Steve

[Søren Dyhr]

therefore should I figure out a way to HARD CODE this number into the area where it is needed?

Make an unstored calcfield on the "subscriper side" and an autoenter or a relation with allow creation of related record on the "defaults" side of the relations def.

--sd