Lock Path (Magic xpa 2.x)
When using an RDBMS to access data, Magic xpa is not aware of the physical location of this data: the data may reside on some remote host machine, but it still appears to Magic xpa as though it were local. In this case, the internal Magic xpa locking mechanism cannot operate, because this mechanism requires all users accessing the same data to share the same locking file. Therefore, when using a Database server to access data, concurrency control must be handled by the Database server, and the External Use setting, must be set to Yes.
If the Magic xpa's internal locking mechanism is to be used in addition to the database's mechanism, Magic xpa must have access to some disk directory that is shared by all the users of this database entry. Such a directory can be specified using this Lock File Path setting.
A Logical Name may be used for this setting.
Relevant interfaces: This property is not relevant for SQLite or Local databases.
Magic xpa Locking
Lock File
Locking Methods
Locking Strategy - Multi-User Considerations
Task Nesting and Locking
