Re: Closing open Win32 Applications

There may be a bug that causes XMLSpy to run in a different user context.

Check out this Microsoft MSDN article for a similar problem/solution in Access.

Comment on Re: Closing open Win32 Applications

Replies are listed 'Best First'.
Re: Re: Closing open Win32 Applications by Anonymous Monk on Dec 08, 2003 at 14:54 UTC
I attempted the context fix from Microsft, but the app still does not close. When I test the application, I create the open instance of XMLSpy by using the standard windows GUI (I click on the shortcut icon). I use pertty much all the other OLE methods with the open window, but I can never get it to quit the application. There must be a difference between an OLE object created in PERL or one created by an interactive user.	[reply]

Replies are listed 'Best First'.

Re: Re: Closing open Win32 Applications
by Anonymous Monk on Dec 08, 2003 at 14:54 UTC

I attempted the context fix from Microsft, but the app still does not close. When I test the application, I create the open instance of XMLSpy by using the standard windows GUI (I click on the shortcut icon). I use pertty much all the other OLE methods with the open window, but I can never get it to quit the application. There must be a difference between an OLE object created in PERL or one created by an interactive user.

[reply]