Suspends data processing, allowing the database to release locks on record pages and make all data in your local Dynaset objects current in a multiuser environment.
Use the FreeLocks statement in multiuser, multitasking environments where there is not enough time for background processing to keep all records current in your recordset. Normally, read locks are removed and data in local Dynaset objects is updated only when no other actions (including mouse moves) are occurring. If data processing is so intense that normal background management of locks is unable to keep up, then you should periodically use FreeLocks to allow the processing that would ordinarily occur in the background.
This function is not needed in single-user environments unless you are running multiple instances of your application.