"Sue" <not-r***@not-real.com> wrote in message
news:lr2d251s279ui8snq6eujrf397v2ckgl8h@4ax.com...
> Hi
>
> Apologies if this is the wrong group.
>
> I ran one of my compiled vb6 programs all last year on this Windows Xp
> PC without any problems.
>
> Now i have started to use it again and i keep getting a "Visual Basic
> Needs To Close" error followed by a "Just In Time" error message.
>
> Non of my error trapping in the app gets called either compiled or in
> the IDE for some reason?
>
> This is what i get from the event viewer:
>
> Event Type: Error
> Event Source: Application Error
> Event Category: None
> Event ID: 1000
> Date: 03/06/2009
> Time: 02:36:24 PM
>
> Description:
> Faulting application trigger.exe,
> version 1.0.0.0,
> faulting module ole32.dll,
> version 5.1.2600.5512,
> fault address 0x00075d00.
>
>
> Basically i have a timer that executes code to download XML files
> using  XML v4.0   MSXML2.XMLHTTP40 every few seconds.
>
> The error now happens every time i run the app but not at any
> particular time.
>
> I am not sure if this is enough information for any of you to have any
> idea what it might be causing this error ?
>
>
> Thanks for any help with this.

>
>If this happens only in the EXE, use OutputDebugString() around the calls to
>create the object, and in various places where you think the problem maybe
>occurring. OutputDebugString() prints the output to a debug viewer, which
>you can view by using the free software:
>
>DebugView:
>http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
>
>Declaration:
>
>Public Declare Sub OutputDebugString Lib "kernel32" Alias _
>    "OutputDebugStringA" (ByVal lpOutputString As String)
>
>Usage:
>
>OutputDebugString "ABC"
>
>Wrapper sub:
>
>Public Sub DebugPrint(ByRef s As String)
>    OutputDebugString s
>End Sub
>

"Sue" <not-r***@not-real.com> wrote in message
news:lr2d251s279ui8snq6eujrf397v2ckgl8h@4ax.com...
> Hi
>
> Apologies if this is the wrong group.
>
> I ran one of my compiled vb6 programs all last year on this Windows Xp
> PC without any problems.
>
> Now i have started to use it again and i keep getting a "Visual Basic
> Needs To Close" error followed by a "Just In Time" error message.
>
> Non of my error trapping in the app gets called either compiled or in
> the IDE for some reason?
>
> This is what i get from the event viewer:
>
> Event Type: Error
> Event Source: Application Error
> Event Category: None
> Event ID: 1000
> Date: 03/06/2009
> Time: 02:36:24 PM
>
> Description:
> Faulting application trigger.exe,
> version 1.0.0.0,
> faulting module ole32.dll,
> version 5.1.2600.5512,
> fault address 0x00075d00.
>
>
> Basically i have a timer that executes code to download XML files
> using  XML v4.0   MSXML2.XMLHTTP40 every few seconds.
>
> The error now happens every time i run the app but not at any
> particular time.
>
> I am not sure if this is enough information for any of you to have any
> idea what it might be causing this error ?
>
>
> Thanks for any help with this.
>
> Sue

On Wed, 3 Jun 2009 14:26:01 -0500, "Ralph" <nt_consultin***@yahoo.com>
wrote:

>
>"Sue" <not-r***@not-real.com> wrote in message
>news:lr2d251s279ui8snq6eujrf397v2ckgl8h@4ax.com...


>In addition you probably should instrument a JIT Debugger. See the following
>slightly misnamed article on how to install Dr. Watson.
>"How to disable Dr. Watson for Windows"
>http://support.microsoft.com/kb/188296/
>
>The EventViewer is giving you some information (we known it is failing in
>OLE) but Dr. Watson will provide additional call stack information that may
>help to narrow-down the location of the error within your program.
>
>Are you also using, or have installed, a .Net Framework development
>platform(Visual Studio 200x) on the box? Various recent MS products will
>instrument the VS.Net JIT when they are installed. This can cause problems
>with some programs. Best to use the more generic Dr. Watson unless
>specifically developing with .Net. The above article will show you how you
>can swap out JITs.
>
>The fact it used to run and now doesn't suggestion that something has
>changed on the box. (Duh! lol) If you are still having trouble, report back
>with Dr. Watson information and also a list of new products.
>
>-ralph
>