I'm not sure if this is the right forum for this, but as the problem hapens during a script run, I might as well.

There are times in a served environment (FM6) when I need to run some replace scripts on a set of records. When this occurs while another using is on one of the records, I get a "cannot modify" halt.

Somewhere I ran across a technique for trapping this error and saving the info as to which record was being hung, then proceeding with the rest of the script. Afterward, either the record being locked could be found (key field stored in a global?) or the script would rerun on just the locked record.

I searched the forum every which way I could think of and drew a blank. Any pointers?

Steve Brown

To trap for errors in scripts you must turn on error trapping when you need it with "Set Error Capture" step.

Any errors generated only exist to the next script step so you must trap for it immediately using the "Status(CurrentError)" function. You can find the list of error codes in the FMP help system under "Status(CurrentError)"