Access 2000 - unexpected shut down

[bigpee]

Hi,

I have suddenly started experiencing a very strange phenomenon.

If I edit a report and change anything in it, when I click on save,
Access shuts down completely without saving the changes !

I have tried all of the various compact and repair scenarios, I've
created a blank database and imported all my items into it - with no
success, finally I've uninstalled and re-installed access again with
no success.

This is drving me nuts !!!!!!!

Regards,
Paul

 

[Allen Browne]

Did you try a decompile?

Try these steps in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Still in the code window, choose Options on the Tools menu. On the
General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
and the Compile on Demand is unchecked.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
the code syntax is compilable, and the VBA options are set to show errors
and avoid this kind of corruption.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[J_Goddard via AccessMonster.com]

Hi -

I'm a little vague on the details, but I had the exact same problem a couple
of years ago (i.e. modifying reports), and it turned out to be a .dll
conflict between MS Access and another running process or application (darned
if I can remember which), and once I stopped that process, MS Access worked
fine.

When MS Access crashes, do you get any indication of the cause at all, such
as a .dll problem? If so, check to see if you are now running an application
which you were not running before.

If I can retrieve the application name from my memory archives, I'll let you
know!

HTH

John