Access 2003 Serious Errors

[Guest]

I am currently developing an application at a client using Access 2003
(11.6566.6568) SP2, running on Windows XP (with latest updates) and linked to
Sql Server.

Sorry for the long post, but I need to try to explain the problem and what I
have already done to try to fix the problem.

I am experiencing complete shut down of Access under certain conditions.
These shut downs are occurring even when I just create a new database, create
a new form, create one button that just changes the Caption of a label when
the button is clicked.

When the problem occurs, I get the "Micorsoft Office Access" dialog box that
says,"Microsoft Office Access has encountered a problem and needs to close.
We are sorry for the inconvience." One option to Compact and Repair the
database. Button to Send error to Microsoft, etc. Required to Exit.

If I open the form in design mode, then just click the "Code" button from
the menu, I get the error.

If I first click on the From selection button at the top left corner of the
form and then click the "Code" button I get the error.

If i click on a section of the form or a control on the form and then clilck
the "Code" button I do not get the error. However, if I then switch back to
the database window and attempt to open a second form in design mode I get
the error.

I have tried many things including: updating Windows and Office; compacting
and reparing the database; importing all objects into a new database file;
starting with an empty database file and more. Nothing has helped.

Does anyone have any idea why this very frustrating situation exists and how
I can fix what ever is causing the problem. I cannot work successfully in
this situation and would appreciate any help.

Mr B

 

[Guest]

Let's go to the obvious first: What happens when you do the same thing on a
different computer? What happens when you run a database created on the
problem machine on another computer? If things run well on other computers,
guess what - it's the computer. Anything else 'flakey' happening on that
computer?

I'd check the hardware including memory. If the machine has multiple memory
cards, you might be able to pull one and see if the problem goes away. If
not, replace the card and remove the other(s). If the problem goes away, you
have a cheap fix. Otherwise there could be other problems like overheating if
this happens after the computer has been running for a while or network
problems if the database is out on the network.

If the problem just started happening, you might be able to use System
Restore to go back in time and fix the problem.

You might try uninstalling Office then doing a reinstall. Uninstalling
Office is very difficult as a lot of junk is left on the computer. Microsoft
has some utilities that can help here. I've found it easier to wipe the hard
drive and start with a fresh install of Windows and Office if there aren't
too many other programs and important files on the computer.

 

[aaron.kempf]

MDB is ****ing crap. It isn't reliable enough for a single record and
a single user.

spit on anyone that uses it.

 

[Guest]

Jerry,

Thanks for the reply.

One of the first things we did was to bring in a laptop and try it. The
same exact thing occurred. Everything else we attempt to do seems to be OK.

The problem seem only to be in someway connected to the VBA code and the
opening of the VBA code editor.

At one point just now, I saw some error about "Runtime". I do not know at
this moment if the runtime version of Access has everbeen install on either
this computer or the laptop that we also used in testing. Is there any sense
that if the runtime version exists on the machine that is developing, that
there is come conflict?

Just a thought.

I have been developing for a long time and have never experienced anything
like this. I just do not know where else to look.

Mr B