Hello Ursus,
thank you for your explanation.
In fact, your hint pointed me to another workable solution - good old user
access groups...
---
Met vriendelijke groet / Mit freundlichen Gruessen / With kind regards
Christoph Bouthillier
p/o\s/t atsign ohnotekstotaaloh nocom
Leave out: \ / oh no
---
"Ursus" <ursus.kirk [at] wanadoo.nl> schrieb im Newsbeitrag
news:46c1e03d$0$304$dbd4d001 [at] news.wanadoo.nl...
>
> "Christoph Bouthillier" <post [at] tekstotaal.com> schreef in bericht
> news:daf77$46c17c08$d4ba06cf$2031 [at] news.speedlinq.nl...
>> Dear Listeners:
>>
>> As the subject line says, I have a database with 2 passwords:
>>
>> password 1 = Access the entire file
>> password 2 = Browse records, Print records, No menu commands
>>
>> All global fields however are editable with password 2. Non-global fields
>> ar correctly protected.
>>
>> Any suggestion/idea about what is going on here?
>>
>> TIA
>>
>> ---
>> Met vriendelijke groet / Mit freundlichen Gruessen / With kind regards
>> Christoph Bouthillier
>> p/o\s/t atsign ohnotekstotaaloh nocom
>> Leave out: \ / oh no
>> ---
>>
>>
>>
>
> Globals are per user fields. Each user can have access ( seperate or
> simultaniously by a network ) and change the values according to their
> wish, or according to the needs of a script. Thus a global might hold
> several values during a session. If you want to protect it, you might
> remove it from the layout and use a text representation instead. Or if you
> realy need the field on your layout you can lock it with a calculated
> result.
>
> Create field gMyfield < text ; global >
> Put your value in it. Now protect it.
> gMyField < textfield , global, Auto-Enter calculation replaces existing
> value, Evaluate Always, By Claculation) > If ( isempty ( gMyField ) ;
> gMyField ; gMyfield )
>
> And what ever you try you will not be able to change the value.
>
> Keep well, Ursus
>
>
> Now you can put it on a layout. Play with it, but NOT
>
