Editing Architecture of Btrieve (section)

==Concurrency==
Btrieve was able to handle [[concurrency (computer science)|concurrent transactions]] in the 6.x series. Before Btrieve 6.0 the engine could only do file level locking or ''exclusive'' locking; from 6.0 onward, records could be locked individually. Locking at the record (or page) level was known as ''concurrent'' locking. The advantages were obvious: more than one client could access the file at the same time, so long as they weren't trying to access the same record, leading to performance increases. Additionally, other clients could read the locked pages, and would not see any changes to a file involved in a write transaction by another process that had locked the record.

MEFS mode did not completely support concurrent locking. If a client started a concurrent transaction and then tried to perform a write operation to a record, the Btrieve engine would return a status code 85 that indicated that the file was locked — even though a concurrent lock was being used.