Access has encountered a problem...

[Lyn]

From time to time I strike a problem where Access will suddenly shut down
while running some code (Dr Watson message), wiping out any forensics
(diagnostic traces such as debug.prints, etc). This is frustrating enough,
but if I step through the same code one instruction at a time, it always
functions perfectly. I have usually resolved the issue by time-consuming
trial and error, making pseudo-random code changes until I end up with
something that functions more or less as I want, but without crashing
Access.

The fact that it works when stepping through, or even by inserting a single
breakpoint, suggests that there is some sort of timing conflict, probably
with asynchronous activity taking place. I have tried inserting lengthy
delay loops at various points (to simulate the breakpoint), but this
strategy is usually unsuccessful in affecting the operation of the code
(other than to slow it down).

I am currently trying to resolve another instance of this problem, so far
without success. I will detail the current problem in a separate post, but
my question here is: is there some logical strategy for troubleshooting
this type of problem other than trial and error? How can I pinpoint the
problem code when Access crashes and leaves no trace, but works perfectly
when stepping through?

Thanks for any insight,
Lyn.

[Tony Toews [MVP]]

Lyn <l.*******@iiNet.net.auwrote:

>From time to time I strike a problem where Access will suddenly shut down
while running some code (Dr Watson message), wiping out any forensics
(diagnostic traces such as debug.prints, etc).

Try logging things such as debug.print using a call to the following procedure.
Change the file name to suit your environment of course.

Sub LogToTextFile(Comment As String)

Open "Q:\1 access\Fleet Mgmt\zzz Service log.txt" For Append As #1 ' Open file
for output.
Write #1, Comment
Close #1

End Sub

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

[Lyn]

On Sun, 21 Oct 2007 22:16:07 GMT, Tony Toews [MVP] wrote:

Lyn <l.*******@iiNet.net.auwrote:

>>From time to time I strike a problem where Access will suddenly shut down
while running some code (Dr Watson message), wiping out any forensics
(diagnostic traces such as debug.prints, etc).

Try logging things such as debug.print using a call to the following procedure.
Change the file name to suit your environment of course.

Sub LogToTextFile(Comment As String)

Open "Q:\1 access\Fleet Mgmt\zzz Service log.txt" For Append As #1 ' Open file
for output.
Write #1, Comment
Close #1

End Sub

Tony

Tony,
Thanks for the great suggestion. I don't know why I didn't think of this
myself! In any case, I have adapted it and it has led to finding a
workaround solution which I think I can live with (the cause the crashes is
still a mystery).

Cheers,
Lyn.

[Tony Toews [MVP]]

Lyn <l.*******@iiNet.net.auwrote:

>Thanks for the great suggestion.

You're quite welcome.

>In any case, I have adapted it and it has led to finding a
workaround solution which I think I can live with (the cause the crashes is
still a mystery).

BTW please send the crash reports to Microsoft. Fixing those problems are a very
high priority within the development team.

And what was your problem? So we'll know for others?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

[Tony Toews [MVP]]

Lyn <l.*******@iiNet.net.auwrote:

>I would still like to find out (at least) whether removing an applied
filter to redisplay the original recordset is somehow bad practice (if not
illegal), or whether I am doing it in the wrong way (I have tried many
variations, all with the same result).

I generally clear the filter (or set it to a zero length string) and setfilter = off.
That's worked for me for years.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

[Lyn]

On Sat, 27 Oct 2007 01:54:26 GMT, Tony Toews [MVP] wrote:

Lyn <l.*******@iiNet.net.auwrote:

>>I would still like to find out (at least) whether removing an applied
filter to redisplay the original recordset is somehow bad practice (if not
illegal), or whether I am doing it in the wrong way (I have tried many
variations, all with the same result).

I generally clear the filter (or set it to a zero length string) and setfilter = off.
That's worked for me for years.

Tony

Yes, that was one of the first things I tried. There must be something
else that is odd about this form :-(

Lyn.