Extended locking, the standard locking method for non-Unix systems in the FairCom DB Standalone Multi-user model, uses ctLOCK_TOP to determine the highest potential offset within a file.
Note: Extended locking will only work if all applications sharing files use the same offset, otherwise locks will not be properly implemented.
ctLOCK_TOP is not an issue with any of the FairCom DB client/server models, which automatically handle locking for any type of FairCom DB client.
When mixing platforms in the Standalone Multi-user model, ensure the ctLOCK_TOP define is consistent between different platforms. Use the lowest common setting to maintain compatibility. For example, when mixing 16-bit and 32-bit applications, use 0x7fffffff. The default settings for Standard libraries are:
Platform |
ctLOCK_TOP value |
---|---|
Win32 |
(ULONG) 0xffffffff |
Mac |
(ULONG) 0x4fffffff |
Unix |
Not implemented |
When using FairCom DB Professional with ctHUGEFILE defined, there are additional limitations.