Hi,
Not trying to hijack or anything, but on the record locking
looping commentary, if I might ask. How best to lock a group of
records in the script before zapping it with a replace?
Thanks,
Laura Z.





---- On    , Todd Geist ([log in to unmask]) wrote:

One further refinement :-)

On Tue, Dec 27, 2011 at 5:30 AM, Corn Walker  wrote:

One refinement is that entering a field is no longer sufficient
to lock a
> record. You should use the Open Record[] command to do so,
which should
> return error 301 if the record is in use.


Don't just check for a 301 error. Check for any error. If any
error occurs
you didn't open the record. So check for Get(LastError) = 0. If
it is 0,
your safe. If it is not 0, your not.

For example, Record Level Access would also stop a script from
opening the
record and it does not return 301. It returns 200.

Todd