Report Crashes Access 97

[jbehrne]

Hi All,

I have been working with an Access 97 database and have come across a weird problem (as of yet I have found no resolution...)! I have a report that pulls data from a query. The query pulls select department data depending upon what department is selected from a dropbox on a form. When the report is opened I receive this error:

Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.

Here is the specifics:

Error Signature:
AppName: msaccess.exe	 AppVer: 8.0.0.5903	 ModName: msaccess.exe
ModVer: 8.0.0.5903	 Offset: 001338e8

This report crashes Access no matter what computer I am using (I am running the .mdb). I can opent the controlling query without problems. I can open the report in design view without problems. I have rewritten the controlling query and the report several times and each time the report still crashes with the above error... If I switch the report to another query (that shows all departments) the report opens fine. Is this error caused by the link to the query? Is there a fix for this?

Thanks,

jbehrne


If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[jbehrne]

Update:

I have written a function that pulls the data from a query and dumps it to a temporary table. The report is then based on the temporary table. This work around fixes the problem - but it still doesn't answer the question of why the link between the query and the report crashes Access. Any ideas or answers?

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[chtullu]

I've also encountered the same problem when using Access 97. I researched it and could find no answer. As the old parrish priest said when asked questions to which there were no clear answers "It's a Mystery

 

[jbehrne]

I guess that answer will have to suffice for now... I'm suprised that MS has no documentation on this bug at all. It is quite frustrating because in this particular database reports that were working as of late last week are slowly falling victim to this bug (this is the 3rd report that is displaying the above symptoms which was working)!

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations