>Hi All,
>
>To make a short story long... two years ago I took a job with a company that has a homegrown foxplus unix system. The idea was since I was up on VFP and came from a foxplus background, I would be the perfect person to maintain the current system while working on a VFP re-write. Of course, as more bugs were fixed and modules and functionality was added to the unix system, no work has been done on creating the VFP system. AND I'M SICK OF WORKING IN FOXPLUS!!!! (sorry)...
>
>We use Samba to allow windows to talk to unix. And the boss just told me I can start writing all new modules in VFP and start rewriting existing modules in VFP and the users can run the VFP and FP systems simultaniously if I can get the VFP modules to talk to the Unix tables. Well, that's better than nothing!
>
>The problem is when I open a foxplus table in VFP and place an rlock() on it, I can then still open up the file in unix and place an rlock() on the same record. So my assumption is recording locking between the systems will be a big problem. Short of adding a logical locked field in every table (which, come to think of it, might be a solution?), does anyone know of a way to get VFP and FP Unix tables (talking through Samba) to reconginze each other's record locks or have any other suggestions to accomplish this?
>
>I will be indebted to anyone who can help me get out of the 20th century and move back to the future!

My condolescences, pal. It's been nine years since I last touched Foxplus for Unix (actually, Xenix)... and did equally hate it. Most of the keyboard shortcuts were different or didn't work, screens could mess up anytime, and there was no decent code editor. Are you using Foxplus or FPU2.6?

Just an idea: if Samba allows you to talk across the OS boundary, could you put your tables on a Windows location and use them from there, hoping it would give you decent record locking?