just a WAG, but if you SET PROCEDURE TO prior to running your menu, does that work?
I must admit I've never seen anything like this happen in all my years.
Can you post the relevant menu code?
>Yes, I've been toying around with the idea of using a replacement, but never get around to it. I guess if I won't check out any replacements, I can't complain about the original, right? Well, actually I can. They have done nothing with it in years and actually just some simple changes would make a significant difference, so I do feel I have a right to complain. <g> > >>You may want to check Replacement Menu Editor for the VFP Editor File #30459 and Visual Menu Designer (Shareware) File #15213 >> >>>I already know that . . . it calls a procedure within the menu. However, I did look and the pathing in the file was incorrect. The VFP menu is so incredibly archaic. It's still requiring the generation step (which I can blissfully forget most of the times because my apps are always EXEs and that happens during the compile), we still have to deal with the nagging and unnecessary "Do you want to save?" question, you can't resize the menu designer form, and navigation is horrible. And then it still uses the LOCFILE function to call a procedure within itself. I can't imagine how the pathing got changed. This is a commercial app based on SBT/Accpac and so it is a bunch of FXPs, stand alone reports, VCX files, etc. Having to generate a menu is something I haven't done in ages! Thanks, Sergey.
