I have seen this problem in other posts - but it seems to be for multi-user environments.

Mine is only used by 1 person at a time - but still I am getting 'record in use' errors. They have started appearing after upgrading to FM7 - the majority when I am using the 'replace contents' script step.

I know there are additional locking features in FM7 - so what would I need to remember to fix this? Do I need to specifically use the 'commit record' step and things like that?

Thanks

I haven't seen this particular problem, but it would seem to me that if you were to launch the script from an uncommitted record and started the replace contents routine, that when the script came to that uncommitted record that you started from, it will interpret it as locked by you, the record's 'owner.' So I'd commit the record first and then proceed with the replace contents script.

Hope this helps,

Dan

Yes, you should specifically use the Commit Record step. It was a good idea in 6, it's critical in 7. Another factor is the possibility of 2 windows of the same data, one of which could have a cursor in an field after editing (just parking the cursor should not lock, but I believe it remains locked after editing until you click out or commit).

A new behavior in 7 is that you must use the commit record step in the master file after editing related records via a script, or the related records remain open. Easy to do, difficult to remember.

There is an excellent article about this by Ilyse Kazar in the migration_foundations.pdf paper, in the Support area at FileMaker.