"Sorry, Access has to close now for some reason or another..." msgs in A97

[MLH]

I get something like this a percentage of the time when
I open an A97 report by dbl-clicking it in the database
window. I can not remember seeing tnis when the
report is opened in code, I can not remember it
happening when the report is opened first into design
view and then into report view. But I can remember it
happening when first opening the report in design view.

Trouble is, this does not happen all the time. Lets just
say less than 10% of the time. Generally, it does not
happen AGAIN upon restarting Access after the error
shuts it down. This unpredictable behavior makes de-
bugging it a trial & error procedure. Using the word
"Description" anywhere for anything is a practice I'm
abandoning. After replacing all instances of that word
throughout my database, I find the anomoly still occurs.

I've spoke of this before in the NG, but the thread is
old and without concrete resolution. As long as this
tear in the time-space continuum persists, I'll raise the
flag a few times each year - just 2C what pops up in
your brilliant minds.

[Tim Marshall]

MLH wrote:

I get something like this a percentage of the time when
I open an A97 report by dbl-clicking it in the database
window.

In order, I'd try:

1) Compile and Save in a code window;

2) Compacting;

3) Proper Decompile;

4) Open an empty mdb and import all objects from the mdb in question

5) Reinstall A97

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[Salad]

MLH wrote:

I get something like this a percentage of the time when
I open an A97 report by dbl-clicking it in the database
window. I can not remember seeing tnis when the
report is opened in code, I can not remember it
happening when the report is opened first into design
view and then into report view. But I can remember it
happening when first opening the report in design view.

Trouble is, this does not happen all the time. Lets just
say less than 10% of the time. Generally, it does not
happen AGAIN upon restarting Access after the error
shuts it down. This unpredictable behavior makes de-
bugging it a trial & error procedure. Using the word
"Description" anywhere for anything is a practice I'm
abandoning. After replacing all instances of that word
throughout my database, I find the anomoly still occurs.

I've spoke of this before in the NG, but the thread is
old and without concrete resolution. As long as this
tear in the time-space continuum persists, I'll raise the
flag a few times each year - just 2C what pops up in
your brilliant minds.

Do you have any code behind the report? Like in the OnOpen event,
OnClose, etc?

If so, you may want to put in some code that writes to a text file and
appends the messages. Open the text file (see Open in help) and write a
line and time to the file and close it. Ex:
Open "C:\TESTFILE.Txt" For Output As #1' Open file for output.
Print #1, Now() & " Passed this section" ' Print text to file.
Close #1

WHen it aborts, you can find out how far it got before collapsing.

[David W. Fenton]

MLH <CR**@NorthState.net> wrote in
news:af********************************@4ax.com:

I get something like this a percentage of the time when
I open an A97 report by dbl-clicking it in the database
window. I can not remember seeing tnis when the
report is opened in code, I can not remember it
happening when the report is opened first into design
view and then into report view. But I can remember it
happening when first opening the report in design view.

Trouble is, this does not happen all the time. Lets just
say less than 10% of the time. Generally, it does not
happen AGAIN upon restarting Access after the error
shuts it down. This unpredictable behavior makes de-
bugging it a trial & error procedure. Using the word
"Description" anywhere for anything is a practice I'm
abandoning. After replacing all instances of that word
throughout my database, I find the anomoly still occurs.

I've spoke of this before in the NG, but the thread is
old and without concrete resolution. As long as this
tear in the time-space continuum persists, I'll raise the
flag a few times each year - just 2C what pops up in
your brilliant minds.

Typically, this kind of problem is caused by something to do with
the printer driver for the printer that is saved with the report.

And printer drivers can be buggy because of dodgy video drivers
(Windows is designed so that printers use video drivers to do
certain kinds of rasterization in order to improve WYSIWYG), so I'd
try using a different printer driver and check to see if I had the
most up-to-date video drivers.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[MLH]

All EXCELLENT suggestions. Am going to try
them one-by-one. Because of the intermittent
nature of the problem, it'll take me some time
to debug. This thing's like an STD - I wouldn't
wish it upon anyone. Once I've pretty well de-
termined that its been eradicated, I'll follow back
up with a report.