> The database is open on the desktop, using my password. The script is
> being run by me. I'm pretty sure this is Filemaker behavior, not OS.


Doesn't make any difference whether it's opened on the desktop or on 
the server.  If the user has put the focus on a field AND started an 
editing process and then NOT committed the record in any of several 
ways, then the record is locked.  And if it is locked, then it can't be 
edited by another use (or in this instance API).  And you get the error 
you describe.  Incidentally, merely putting the cursor into a field 
does not lock the record any longer. This was a change introduced in 
2004 with FileMaker Pro 7.

You could possibly create a single line ScriptMaker script that runs a 
Commit records, and then call it first. Or, you could trap for a record 
lock.

At least this is not a process lock.  Those are really fun.

HTH

Steven
-- 
Steven H. Blackwell
Partner Member, FileMaker Solutions Alliance
FileMaker 8 Certified Developer
FileMaker 7 Certified Developer
_________________________________________
"The commitment of our Fathers is now the calling of our time."
_________________________________________

FileMaker Security:  The Book
http://www.filemakersecurity.com