Access Report Crashes Database on Open
I have a fairly large report that serves as a production report for several employees. There is a faily complex query that runs it. This query links together 4 queries and brings in one table. The query runs just fine, but when I try to run the report, access crashes and gives an unexpected error message.
The report worked fine yesterday and this morning. I added two fields to one of the subqueries and imported them into the query that serves as the report's recordsource. After that, the report crashes every time.
I've tried the following:
1) Remove the fields / changes that I made to queries this morning.
2) Remove the changes that I made to the report.
3) Add them all back
4) Compact Database
5) Repair Database
6) Copy Report over and try to run the copy.
Anyone know why this report would continue to crash the way it is? I can't seem to fix it. The query runs fine and populates the data correctly. Nothing looks strange in the query. Access 97 database.
Thanks
The report worked fine yesterday and this morning. I added two fields to one of the subqueries and imported them into the query that serves as the report's recordsource. After that, the report crashes every time.
I've tried the following:
1) Remove the fields / changes that I made to queries this morning.
2) Remove the changes that I made to the report.
3) Add them all back
4) Compact Database
5) Repair Database
6) Copy Report over and try to run the copy.
Anyone know why this report would continue to crash the way it is? I can't seem to fix it. The query runs fine and populates the data correctly. Nothing looks strange in the query. Access 97 database.
Thanks
Last Comment
ASKER
Error Information (Error Signature):
AppName: msaccess.exe AppVer: 8.0.0.5903 ModName: msjet35.dll
ModVer: 3.51.2026.0 Offset: 0002603d
Screenshot of error attached.
AccError.JPG
AppName: msaccess.exe AppVer: 8.0.0.5903 ModName: msjet35.dll
ModVer: 3.51.2026.0 Offset: 0002603d
Screenshot of error attached.
AccError.JPG
Have you tried to decompile the database?
Run this in your command prompt :
"C:\Program Files\Microsoft Office\Office12\MSACCESS.E
Just replace this with your correct path.
Otherwise, try and create a new database and import all info from the failing db.
Run this in your command prompt :
"C:\Program Files\Microsoft Office\Office12\MSACCESS.E
Just replace this with your correct path.
Otherwise, try and create a new database and import all info from the failing db.
ASKER
Chris,
I just created a blank database on my desktop and imported everything from the database to it. The report still crashed the system.
I deleted the report and tried to re-import it and got the same results.
The rest of the database works fine, I think it's isolated to the report and unfortunately, I don't have a backup. Any other ideas?
I just created a blank database on my desktop and imported everything from the database to it. The report still crashed the system.
I deleted the report and tried to re-import it and got the same results.
The rest of the database works fine, I think it's isolated to the report and unfortunately, I don't have a backup. Any other ideas?
Yep. Start again. Sorry.
Chris B
Chris B
ASKER
As strange as this sounds, earlier I reverted the changes made to 3 of the subqueries, and changed the report back the way I had it this morning (I can still open it in design view). I left the items on the report recordsource query (they were listed as Expr1, Expr2, etc).
When I removed them, the report fired off correctly.
When I removed them, the report fired off correctly.
Curious. Perhaps corruption is not the issue. You may have done something to the report which made it unusable. Take a copy of the working db, then try editing the queries/ report once more, doing one step at a time the running the report until you get where you want to be or it falls over. In the latter event, try to find another way to do what you seek. Every time you make a change, take a copy of the db so you can revert quickly. (Standard Access development tactic).
Chris B
Chris B
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks, I ended up finding that the solution was just a small oversight on my part coupled with joining tables incorrectly in one location. The long load time for some of the reports and the crashing was due to access pulling too many records in the query because the joins were not working correctly.
Thanks for your help.
Thanks for your help.
Microsoft Access
Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.
226K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Chris B