>>>>>FLOCK() AND RLOCK() return .T. and not actually lock. With free tables everything works as expected.
>>>>>
>>>>>>>I've got a verified situation where RLOCK() and FLOCK() don't work when issued against a VFP5 database table under NetWare 3.x. Everything works fine is the app is moved to any not NetWare disk (NT, Win95). I've tried flagging the files as shareable and that doesn't work.
>>>>>>>I've tested the situation in 2 different 3.x networks.
>>>>>>>Has anybody experienced this situation?
>>>>>>Does it flock() and rlock() return .t. and not actually lock, or does it return .f. when it should return .t.?
>>>>
>>>>I have not narrowed my problem to this specific cause, but I am having update conflicts with certain tables even though I am using RLOCK(). We are using Netware 3.12, and the tables are on the server. Please let me know if you find out more about this problem, it could clear a lot of things up for me.
>>>
>>>
>>>Eric,
>>> I am sending you the procedures we have been using for a while with fox dbfs and novel 3.x here at Gilbarco.
>>>we have switched to novell 4 now but you can move these to 5.0 and give them a try.
>>>
>>> Hope this helps
>>> Jeff Butler
>>
>>Thanks Jeff...
>>did you send them e-mail? I haven't gotten anything yet...
>>
>>Nice hat...
>
>Yes I did and you should have them by now. Send me an email to jeff_butler@gilbarco.com
>with your correct address. I will try again.
>
>Jeff
>
>The hat just covers the bald.

Thanks Jeff... that's a pretty cool little procedure. I'll see if I can implement something like it.