>My situation has degraded significantly. I now have living somewhere in the electronic world behind my computer screen a menu definition that no longer lives in file form. I have renamed my menu (and redirected the DO mymenu.mpr command), deleted all mpr, mpx and any other files that even looked at me sideways, modified and saved the menu, generated the mpr, compiled into mpx, and recompiled into exe, run and the old %$#!@@ menu shows up!. This is ony happening in exe; when I run the program from the project manager, I get the right menu.
>
>
>I am not a superstitious man, but I am starting to believe I need a menu exorcist.
>
>WTF am I doing wrong? I have never had this problem before?!? Should I quit my programming business and just work on cars?

USE your_project.pjx
blank all field timestamp
use
build exe your_exe from your_project

Between first and second line, you may take a look at the timestamp field... or create a temporary index on the timestamp field, just to see the chronological ordering of files in your project. The glitch I've sometimes observed with generated menus is that it doesn't actually use your .mpr file - it's there just for your reference, so you may take a look at it; once you've included the menu in a project, it will generate a temporary .mpr upon every build, and probably delete it afterwards, not touching your physically present .mpr file on disk. Just try to add a messagebox in the generated .mpr and see what happens after a build. Having a weird timestamp may add to the confusion. Blanking the timestamps should clear the matters in forcing the project manager to re-compile and re-generate all stuff it finds.

Let's adjust our watches, officers... for those with old watches, it's twelve minutes to noon; for those with digital watches, it's two sticks, upside down chair and the snowman.