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."
Charlie
>>Do you have any APP/EXE files included in your app?
>
>Sure do...lots of em. The main program is an EXE (that is where the MPR is built into). Also have four other apps that instantiate objects right out of the gate. None of them use menus.
>
>My next step will probably be to make the MPR external and see if she still has the problem, but I am not even sure what that would show.
>
>Joe Kaufman
Charlie