[Bug 1071] - fixme:file:UnlockFile not implemented in server AND fixme:file:LockFile not implemented in server

[wine-bugs at winehq.com]

http://bugs.winehq.com/show_bug.cgi?id=1071





------- Additional Comments From pmcnett at pm-sc.com  2003-01-13 17:06 -------
The file locking issue described here also affects Microsoft Visual Foxpro.  It will not hang Visual Foxpro, however, unlike what was reported for Access and BDE.  Instead, Visual Foxpro will think it has a lock when in fact it does not, which will cause a surprise for people when they move their app to multi-user or multi-instance!  The debug output is as follows:  fixme:file:LockFile not implemented in server fixme:file:UnlockFile not implemented in server  This bug needs to be fixed before Visual Foxpro developers can deploy to Linux/Wine.  So much existing Foxpro code relies on getting file locks and range (record) locks.  It is necessary to provide primary key values for native visual foxpro tables.  If the record isn't actually locked, duplicate key values could be assigned.  To reproduce the problem in Visual Foxpro, start up instance 1 and in the command window type:  create table test (cid c(32)) use in test use test shared insert into test (cid) values ("1") insert into test (cid) values ("2")  Now fire up instance #2 and in the command window type: use test shared browse  Keeping the browse window open, click on the command window and type: ? rlock()  The "Record Locked" message should appear in the status bar.  Switch back to instance #1 of VFP and type:  browse  Now, change the value of record #1.  Normally, this would be illegal since instance #2 has that record locked, but because locking hasn't been implemented in Wine you will be allowed to change the field without raising an exception in VFP.  This will cause subtle problems that may not be noticed by Visual Foxpro developers until too late!!!  (Note: to successfully run VFP you will probably need to apply the fix for the mouseclick problem by Duane Clark:  found in the activity for bug 434.  Either that or don't click with the mouse in the command window!)  (Note: Samba has file locking correctly implemented... can their implementation be worked into Wine?  For example, if I run Visual Foxpro on a Windows client, and the test table described above is located on a Samba share on Linux, the file and range locks will behave correctly.)  

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1071>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.