Well, I sure hope Elyse saw your suggestion and that it does the trick for her. All of us were sure stumped on this one <g>. I've never used LOCFILE(), so I'd have been totally batty before long. Thanks for interesting explanation.

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