Access 97 closing when viewing reports

[mabris]

I have developed several databases in Access 97 (my employer doesn't want to upgrade because of conversion issues). While running these databases under both WIN2k and XP I have a probelm with the appilcation closing when I open a report (it comes up with an "Send error report?" dialog and then Access closes.) It does this sporadically, but it seems to happen more often when the report is based on a query that has its SQL defined by a VBA module. It still does it, though, when it is based on a standard defined query.

Does anyone know of any issues that might be causing this? Some of the reports are based on very simple queries, but they still exhibit this behavior. I have opened the quires themselves many times without incident, so I know that they are not the problem.

 

[mabris]

If it helps at all, I also get this error when trying to open a report in design view as well.

 

[alvechurchdata]

Does anyone know of any issues that might be causing this?

You'll get more of an answer in one of the Access areas - try

http://www.tek-tips.com/threadminder.cfm?pid=701

Microsoft: Access Queries and JET SQL

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[ceh4702]

What do you expect from a Microsoft Product?

Might try increasing the timeout or something.

I dont have much love for Microsoft databases.

If you do not like my post feel free to point out your opinion or my errors.

 

[ZmrAbdulla]

Go to your VBA window(code window) and from Debug menu try to compile your database. There may be some error on your code.

________________________________________________________________________
Zameer Abdulla
Visit Me
Children are poor men's riches.

 

[flugh]

I had "really odd behavior" for a while like reports crashing Access, Access silently just refusing to open forms, etc. I realized some of the field names in my tables were not exactly reserved keywords, but the names of functions and properties Access uses. After renaming things to "nname", "ccomment", "ddate", etc, things have worked fine. Maybe you have a similar issue?

----
JBR

 

[SQLSister]

We have a printer driver issue that causes this behavior. The wierd thing is that it works just fine sending the report to the printer (or the preview) if some other printer is the default printer and then you manually chnage to that printer after you get the print menu open. This esepcially happens on XP machines. So it may be a problem like this and not totally an Access problem.

Does the same thing happen when you run the queries as the basis for a form? If not, then maybe it is the printer driver that is at issue. Since I use a differnt printer than many of my users, it took me a long time to figure out why I could print and they couldn't. Now if only the printer company would fix their driver.

I'm not saying this is your issue, just throwing it out as a possibility.

Questions about posting. See faq183-874
Click here to help with Hurricane Relief

 

[mabris]

The print driver thing sounds like a promising lead. The queries don't produce the crash when opened in a form or when opened by themselves. Additionally the reports crash opening them in design view too.

BTW, what kind of printer was causing the problem. In my case, it may be our HP-4650.

 

[willir]

mabris
Hopefully this problem has been resolved, but...

I had a simialr problem to what you discribed a few years ago. Traced it to lack of disk space for the temp files.

Make sure you have sufficient resources to run access including adequate space for temp files. It depends on design, but I find the report module takes more resources.

Also,
- try loading and designing the forms on another similar or better PC to see if the problem is restricted to one PC.
- if the reports still crash, you may have corruption. Import the database into a new database.

Richard

 

[mabris]

just a thought, if it is a print driver issue, do you think setting the layout for print property to no will help?