It doesn't happen with WinXP on an NT4 network, FYI.

But - this does sound suspiciously like a problem that came up with the introduction of Netware 3.0 (might have been called NW 386 back then, my mind is going). This problem surfaced with any program written in RM COBOL, which at least one major and very popular accounting package was, as well as a lot of programs you'd never suspect. If I recall correctly, they didn't have a name for the issue but it sounded a lot like a problem with opportunistic locks. It's been a long time, but I believe the issue was that a station might issue a read lock on a record, and then later attempt to issue a read/write lock on the same record. Prior versions of Netware allowed this, NW 3 did not. I believe the error was much like the one you are seeing, in that a user could open the record, but not save changes. You might want to look at the Client32 properties and change the Oplocks setting and see if that helps. Novell, and to a lesser extent, Microsoft, alter the default setting of Oplocks with each new update of their client software. VERY annoying.

HTH,
Randy

>Could someone confirm this possible bug with VFP7 SP1 with menus on a netware volume? Could somebody try to duplicate with different Windows OS and different version of netware? Many thanks.
>
>Title: VFP7 SP1 menu read-only on Netware drive
>
>Steps:
>Using VFP7SP1...
>1) Create a project called test on a netware drive
>2) Add a menu called test to project. Save and close menu
>3) Open menu and modify, then attempt to save menu.
>4) Message "File test.mmx is read-only".
>
>Expected Results:
>Menu should save without displaying "read-only" message above.
>
>Notes:
>- I am using Windows 2000 Pro SP2
>- Netware drive is Netware 5.x
>- Problem does not appear if project and menu are saved on local C drive