Access Database crashes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have developed an access database from scratch. Periodically, 1 week or 2
weeks, the database will crash. I get the error message "Microsoft Access
has encountered a problem and needs to be closed." I select the option to
compact and repair the database. The database opens fine. I select ctrl g
to open the debug window, the database crashes again. I am not able to do
anything with the database.

Next time I open the database, there is one module (module1) that I delete.
Once I delete this module (which contains the mouse wheel disable code on the
Microsoft website), I am able to get to the code window. I compile the
database without error. I re-import the module1. I am able to work in the
database in design mode without a problem. I start/open any form in runtime
mode, Microsoft Access just disappears/closes from my computer. When I try
to open the database again, I get the same results, Microsoft Access starts,
then disappears. However, if I reboot my computer the problem goes away. I
am able to use the database without problem for another week or two until the
problem happens again. This has been an on going problem for 2 months.

The database is now going into beta, and will go live shortly.

Does anyone have any suggestions?

--
Roger Maniccia
emdeon
26 Century Blvd
Nashville, Tenn
615-886-9031
 
Roger

This might be caused by fragmented code.

After backing up the file, run a decompile on the database. Use a run
command starting with your Access exe similare to this:
"C:\Program Files\Microsoft Office\Office11\msaccess.exe" /decompile
"C:\YourDBfile.mdb"

This will strip out any code fragments. Compact the db, compile and close.
You should see quite a decrease in file size.

Re-open it the regular way.
 
Bill,

Implementing what you suggested worked. Thank you for your help.
--
Roger Maniccia
emdeon
26 Century Blvd
Nashville, Tenn
615-886-9031
 
I reccomend not using MDB for anything important.

it's not stable enough for a single record and a single user.

Access Data Projects allow you to re-use a lot of your existing forms
and reports.. but it works against a REAL database _ENGINE_.

MDB doesn't have an engine.
It is for kids.

-Aaron
 
My pleasure, Roger. Whenever I get a database that starts corrupting
frequently, I decompile it. But be careful. It's undocumented and could
theoretically make your file toast.
 
what this Jerry guy is trying to say is that there are many reasons
that Access MDB 'gets corrupted'.

a) do you run the MDB across a wired network
or
b) do you run the MDB across a wireless network

if either of those are true; you can't have any expectation of
stability or performance.

MDB is DED.

-Aaron
 
what this Jerry guy is trying to say is that there are many reasons
that Access MDB 'gets corrupted'.

a) do you run the MDB across a wired network
or
b) do you run the MDB across a wireless network

if either of those are true; you can't have any expectation of
stability or performance.

MDB is DED.

-Aaron
 
Back
Top