How can I lock fields of a record, but not all fields?

[James Steele]

Ok here is what I need to do.

I have a database with many fields used to controlling the disposition of material.

I also have a need to lock this data after it has been approved. (no problem with this).

Now here is the issue.

I need all those fields locked with the exception of 3 fields that need to be edited at a latter time,

These fields would be for such things as entering in a RMA number, when the date replacements have been brought in, or a closed date when the item record has been finished.

How can I lock fields of a record, but not all fields?

James

FM 8.5 Pro/Advanced

FM Server 8

[Steven H. Blackwell]

You could go ahead and lock the record. Then for the 3 fields, enter the data via script and set the script to run with full access privileges.

Steven

[James Steele]

This might work. Will I have to have a new window for this or is there a way to enter the data from strait into what looks like the same fields?

Where do I set the script to run with full access privileges? I have seen it before but now I can not find where I saw it.

James

[Steven H. Blackwell]

Use the custom dialog Script step to create your UI for this. Run script with full access privileges is at the bottom of the scriptmaker window.

Steven

[James Steele]

Are you talking about the custom dialog box in the script as the UI?

This would cause a problem as they slowly add additional fields say 5 or 6.

Or is there a way to create a layout and then run that layout with full access?

I have tried having a script open that layout however that did not allow the editing of the fields.

Thanks

James

Edited February 7, 2007 by Guest

[Raybaudi]

Hi

it depends in wich manner you have loocked the record.

If you loocked it with the use of privileges, but still the user can see the fields, sure he can insert the cursor into those fields, too.

So a script:

Go to Portal Row [No dialog; Get(PortalRowNumber)]

Show Custom Dialog ["Complete the 3 fields"; DB::field1;DB::field2;DB::field3]

may solve your problem