[AccessD] Access97 on W2000 crashes

> No, it was a simple line like
>   Debug.Print "Records:", lngRecordCount
Well, it looks simple but it implicitly uses Long to String conversion, it
does use tabbed formatting of output etc.
Did you try to comment and to replace it with just

Debug.print

?

It may happen VBA didn't compile/execute lngRecordCount assignment code line
at all because you commented out the only(?) line where this assignment was
used etc.

<<<
so I just commented it out. Still wondering.
>>>
Yes, it happens sometimes - this "automagical" bug fixing.

But I'm usually trying to avoid that by any means and to find the real cause
of the
troubles for me and my customers to sleep well :)

Shamil

----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Monday, January 09, 2006 7:00 PM
Subject: Re: [AccessD] Access97 on W2000 crashes


> Hi Shamil
>
> No problem.
>
> No, it was a simple line like
>
>   Debug.Print "Records:", lngRecordCount
>
> which "can't" fail. But it did.
> However, I did not do the import-to-new-thing which might have cured the
issue. In production code no Debug.Print is needed, so I just commented it
out. Still wondering.
>
> /gustav
>
> >>> shamil at users.mns.ru 09-01-2006 16:24:01 >>>
> > It was the line with Debug.Print (left in the production code) that
caused
> the crash!
> I did misinterpret your advice, Gustav, sorry.
>
> But was that just:
>
> debug.print
>
> i.e. debug.print of an empty line or it had some stuff to debug.print?
>
> I guess the problem was with debug.print's parameters?
>
> In the cases like Andy's the only way to find the problematic code is to
use
> detailed logging - simple text file I/O should be used for that with file
> open for append/close for every log record write...
>
> To find a stable workaround the source VBA code line(s) resulting in the
GPF
> should be found - trying to "solve" the problem with "blind" installation
of
> different updates is a pure guessing/gambling...
>
> Shamil
>
> ----- Original Message ----- 
> From: "Gustav Brock" <Gustav at cactus.dk>
> To: <accessd at databaseadvisors.com>
> Sent: Monday, January 09, 2006 5:50 PM
> Subject: Re: [AccessD] Access97 on W2000 crashes
>
>
> > Hi Shamil
> >
> > It was the line with Debug.Print (left in the production code) that
caused
> the crash!
> >
> > /gustav
> >
> > >>> Gustav at cactus.dk 09-01-2006 14:23:14 >>>
> >
> > I had a similar thing which I tracked down to a line with Debug.Print.
> Commented this out and the code ran, believe it or not.
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com