I have a Access 2003 database that has been steady for over 4 years now and it recently is crashing. It is happening when working in reports in design view but not the same reports. I have recently done some changes with the same database in Access 2007 and wonder if switching between the 2 would have damaged it. I then searched your database and have fixed up the following;
I did have Auto Correct on and have sinced turned it off and compacted,
I have also compiled the code (there were a few problems which I have hopefully corrected).
I have checked references and have the following on - please let me know if I should take any of them off - VB for applications, 11 object library, OLe, ACTIVE x objects 2, DAO 3.6 and for some unknown reason MS Scripting Runtime ((I am not using run time anymore can that go )
I also created another Access 2003 database and imported everything but this did not correct the error.
If I move the database onto the new machine with Access 2007 the problem does not occur plus I think it seems to happen in 2003 when I try to do things quickly as if it cant keep up with me. But this is a fast machine and has held the database successfully for years. It is definitey something I have done.
The problem has recently arrisen after I have done a few things. I imported code from one of your guys (he was very helpful and I doubt it was that and I have removed everything I hope that he sent me)
I have deleted a number of tables, queries forms and reports that were no longer being used ( I did use the Access 2007 machine for this plus object dependencies for this as it made it much easier) but as said before I have taken Auto correct off and have compacted again.
Sorry one more thing, the message I get when I pressed the debugger when it crashed last is Visual Studio Just in Time debugger - An unhandled win43 exception error - no installer debugger has Just in Time debugging enabled - it then tells me to enable it. But I am not running Visual Studio.
When I first got Access 2007 last year I tried to create a run time version of this particular database. I did have problems with this and have sinced stopped it. But this current problem has only happened in the last week and I doubt it has anything to do with runtime.
Any help would be appreciated.
Start Free Trial
