In general, Access 2003 is very stable, but there are some unfixed bugs you
must work around.
1. Any database?
You say it crashes any time you open a database?
Can you open Northwind okay?
- Yes: the problem is with the database.
- No: the problem is with the Office installation.
Will assume Yes.
2. Startup
You say it happens at startup. Are you able to hold down Shift to bypass any
startup form or AutoExec macro, and get in? If so, rename the macro, and
disable the startup form under Tools | Startup. This should let you take
further steps.
3. Name AutoCorrect
Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation:
http://members.iinet.net.au/~allenbrowne/bug-03.html
Then compact the database:
Tools | Database Utilities | Compact
4. Form with subform
If the database crashes using a form with a subform, open the subform in
design view, and add a text box for the foreign key field (the one named in
the LinkChildFields property of the subform control). There seems to be a
bug with the AccessField type, and you can work around it by providing a
control so the object is of type Textbox instead.
5. Decompile
Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then compact the database again.
6. Circular logic
If none of the above apply, look for any logic where one thing could trigger
another that could re-trigger the first. Anything in the Current event of a
form is a likely candidate.
7. Subqueries
If none of the above apply, are there any subqueries (SELECT statement
within another query statement)? These can be treacherous in JET.
Further suggestions in:
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html