>Naomi,
>
>Yes, this is definitely a problem. You didn't mention where this code should go but I assume it is in the Click method of ctmenus.cfileexitbar.

Yes, that's what I meant. We have the exactly same code in cmdExit on the toolbar. I fixed it there long time ago and forgot, because we usually do it from the toolbar and not from the menu.

It also looks like you have added a custom property (lDebugDisableAppQuit) to your application object. For us who don't have this property, it looks like all we have to do is remove the "RELEASE goapp" statement since goapp is released in capp.capplication.onshutdown upon a successful call to the Cleanup method.

That's probably right. I didn't know it's our own custom property, but I take your word for it. My colleague Jim is very knowledgable MM developer, so he knows all ins and outs of the framework and might have added these properties before I joined the company.
>
>-Dan
>
>>Hi everybody,
>>
>>Try to reproduce the following problem: open several forms, type something and then go to the menu and try to close the application using Exit. On the question: Do you want to save changes? Answer Cancel. Then go to any other menu item. You'll get the error goAPP is not the object and the only way out is to kill the application.
>>
>>Here is a quick and simple fix:
>>

>>local lnYesNo
>>store 0 to lnYesNo
>>
>>if vartype(m.goApp) = "O" && if an application object available?
>>	if m.goApp.lDebugMode and !m.goApp.lDebugDisableAppQuit
>>		lnYesNo = MsgSvc("quitapp")
>>		if m.lnYesNo = IDYES
>>			goApp.onShutdown()
>>		else
>>			return
>>		endif
>>	else
>>		goApp.onShutdown()
>>	endif
>>else
>>	clear all
>>endif

>>
>>Thanks in advance.