>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?

I do not remember what kind of problem my example causes, but if the owner of a table is not a valid NetWare user-id, you get errors when running an app. In the Netware database table directory execute a "NDIR". This will list the directory of the files in the directory along with the Owner names in the right column. You will need to change the owner name of any file with owner= "N/A". I think you can issue: NDIR /OW EQ "N/A" so Netware will only list files where owner="N/A".

I usually set up a new UserID in NetWare that is the owner of the application and use this user as the owner of all the files. The owner can be defined through NetWare's "FILER" executable.