>Yes, I believe you are making an incorrect assumption. The Project Manager does quite a lot of work for us. I just double checked this with my live project and the following is fine (note: VFP 3.0b):
>
>My MAINPROG.PRG has a line DO MAINMENU.MPR
>
>I deleted my MAINMENU.MPR file from my project directory.
>
>I deleted my mainmenu from my Project Other/Menus tab (but didn't remove it from the disk!)
>
>Then I clicked on build. I didn't mark rebuild all.
>
>After the build, the project manager had added the MAINMENU.MNX to the Other/Menu tab
>
>A MAINMENU.MPR file has been regenerated in my project directory. MAINMENU.MPR is NOT included anywhere in the project (except as built into the EXE--which is transparent to me).
>
>So, as far as I can tell, if you have DO MYMENU.MPR in your app, then you'll end up with the MYMENU.MNX in your project whether you want to or not. In fact, I couldn't find any way to "accidentally" remove it--every build re-included it. I never use genmenu except when I want to check menu syntax...
>
>This has been really odd, and a useful way for me to avoid my own programming problems , but I believe an interesting possiblity was posted earlier today by G. Tasker (???)...
>
Nancy,

I ran into this behavior about five years ago or so in FPD 2.0. The exact same thing that's Elyse describes was happening on site, but couldn't be replicated in the development environment. Finally, after a lot work, I found the answer that I've described in this thread. The key was the appearance of the LOCFILE() dialog. For various reasons, including the difficulty connected with trapping errors, I had avoided its use. Simply changing the procedures to command calls to prgs fixed it, and I haven't had any problems similar to this since (5 different versions of FoxPro). It also made maintenance a little easier by allowing me to go straight to any program called by the menu without having to open the menu, locate the call, etc.

George