I agree with pcelba.
Locks will be requested via client OS -- YET, ultimately, the file system of the server OS (in this case the NAS) will be the determining factor if locks are supported.
The best way to find out if the capability EXIST by attempting to LOCK via TEST DATABASE.
=NerdsOfTech
Main Topics
Browse All Topics





by: pcelbaPosted on 2009-07-28 at 13:41:43ID: 24965001
Windows PC is opening the file BUT the logic behind it must call the File system on the NAS to fullfil this request. Same procedure is valid for file locking. The NAS must provide interface compatible for Windows file sharing. If the NAS provides just FTP access you can open and read/write the whole file but you cannot lock single records.
All locks must be handled by the file system where open files are stored. The file system only knows who is accessing the file and it is independent on fact if it is W2K folder or shared drive on the NAS. Local Windows PCs are just passing lock requests and waiting for File system responses (it is done through local OS, of course). Windows client PCs don't know about each other so they cannot handle locks on files shared by anybody else.
The Clarion database has its own set of lock commands which is again implemented through OS kernel calls. You can simply test how locks are handled by attempting to edit one data records from two or more PCs. Depending on application design you may observe following behaviour:
1) All instances will allow record editing, the last save is the winner.
2) All instances will allow record editing, the record change by another user is tested before saving.
3) Only one instance will allow record editing, all others must wait.