>My point is that if any of the other projects includes the menu file in question, they must be rebuilt as well. Just because the menu file isn't used in another app doesn't mean it didn't get pulled in.
>
>There is nothing flakey about the way this works, even though it seems that way now. I've experience the same sort of effect with classlibs. If the old menu file is no more, yet you see references to it, it must be that is still exists somewhere, but in another package. I'm guessing it's in some other APP/EXE file. The file doesn't even have to be in the EXE you're currently running. If you have a loader program that calls your main app, and it's totally separate, be sure it doesn't have the menu file included in it. As the spaghetti sauce commercial says, "It's in there."

You are correct...there was another APP with the MRP in it. This wouldn't have bothered, except the reason it was pulled into that app was because of one spot where we refresh the menus if a report is previewed (because of the VFP 5 bug that would cause the menu to go south in such a case). Our user in question was one of the only people to use the part of that sub-app that refreshed the menu (to the wrong MPR), and so she got the errors.

Thanks for your help on this! Yes, multiple packages/files will probably be the death of me. If only I had organizational skills to match some of my coding skills, I would be set *smile*

Thanks again everyone for your help!

Joe Kaufman