DB Crashes when Form is Opened?

[Yes2man]

Hi All - I really hope someone can help...

I am using Access 2003 and I have two forms that just recently started to
crash the DB when I try to open them from a command button on the main form
(switchboard), I get "Microsoft Access has encountered a problem and needs to
close" dialogue box. They also crash the system when I try to open them
directly from the forms tab. I can't open the forms in design mode (which
also generates the dialogue box), although I can access the code and the
table where the form gets it's data.

What is strange is that I have many forms, but only these two now generate
this error, and they both worked just fine up until a couple of days ago, and
I didn't make any changes or updates to either of them.

This is what I've tried so far - Compact and repair, which didn't work. I
have a backup copy of the DB and when I open the DB from the DVD (read-only),
the forms work fine, but when I replace the whole DB to the HD (to replace
the old one) it crashes (??). I also tried deleting the corrupt form and
importing the working form from the backup, but it crashes too (??). I also
tried creating a new clean DB and then importing the working copies from the
backup, but that crashes when you try to import it (??). Lastly, I also tried
to open the DB on another computer, and it crashed there as well...

I have tried to created a new form from the table (which seems to work just
fine) and I also saved the code, so I can re-create the form, but the forms
I've lost are complicated and took many hours to complete, so I am hoping to
save them if I can!

Does anyone know what happened and is there a way I can repair these forms?

Thanks alot in advance!

 

[MikeJohnB]

I could be wrong but, It sounds like you recently insstalled service pack 3
(SP3), if thats the case install the hotfix for that service pack.

http://support.microsoft.com/kb/945674

Regards
Mike B

 

[MikeJohnB]

Just some of the text from the Hotfix blurb, I hope this sorts out your
problems? Please repost if you still have issues.

This hotfix package also fixes the following issues that were not previously
documented in a Microsoft Knowledge Base article:

Access 2003 may close unexpectedly when you do one of the following:
You open a table that contains a LOOKUP field. The table uses the LOOKUP
field to look up data in a table that contains more than 30 fields.

You open a form that contains a combo box that looks up data in a table that
contains more than 30 fields.

Additionally, you receive the following error message:
Microsoft Office Access has encountered a problem and needs to close. We are
sorry for the inconvenience.

When you view the data in the error report, the report contains an error
signature that resembles the following error signature:

Collapse this tableExpand this table
Application name Application version Module name Module version Offset
Msaccess.exe 11.0.8166.0 Ntdll.dll 5.2.3790.3959 45d70ad8

 

[a a r o n . k e m p f]

if your db crashes-- then move to SQL Server.

 

[Tony Toews [MVP]]

Please ignore Aaron's posting as his reply has no relevance to your problem.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Yes2man]

Thanks for the quick reply. I use a company laptop and don't make updates to
the OS, but I checked and the version is XP2.

Since my post, I changed the DB properties to read-only, sinc eht eback-up
worked read-only, and the forms open no problem. Unfortunately that doesn't
help me since I use these forms daily to input and retrieve data.

What could the difference be between opening read-only and editable?

 

[MikeJohnB]

Hi Yes, sorry, I don't have any other ideas on the reason for this. Perhaps
someone else that has come across the same issue will answer. Else repost as
a New Thread in case they think this one is resolved.

Just for info, I use a company laptop but am also a Regional Area
Administrator. however, updates are installed remotely without user
intervention. our company has chosen not to SP3 for some reason. The other
point of note, it is a office service pack and not XP. Help About microsoft
Office Access displays the applied service pack on line 1

Sorry I could not assist you with this issue though.

All the very best

Mike B

 

[Gina Whipp]

The update MikeJohnB referred to was to Office not to your Operating System.
Check to see what updates were applied to Office and/or Access

 

[Yes2man]

MikeJohnB -

Thanks very much for the help. I will check Office version and see if the
hotfix solves the problem (if I can get the system admin to install it for
me...).

Gina Whipp - Thanks to you too!

Does anyone else have any ideas on what could make these forms just crash
like this?

 

[a a r o n . k e m p f]

Jet fucking crashes.

Every fucking day, somewhere in the world-- Jet crashes.
Maybe you stack a query on top of a query-- and it crashes.

Either way-- you ask for trouble by using an obsolete database.

Move to 'Access Data Projects' if you give a shit about your data or
your clients.

-Aaron

 

[Tom]

Google "Fixing a Corrupt or Problem Access Database v4.5".

There is a fairly lenghty list of troubleshooting steps you can follow
that may or may not help.

Good luck

Tom

 

[a a r o n . k e m p f]

wow I made it _ALL_ the way to page 1
---------------------------------------------------------------------
3. Repair the Database.
3.1. Get everyone off the database.
3.2. With JetComp.
---------------------------------------------------------------------


That right there-- is the part that makes me fucking puke.
That right there-- is the part that makes me fucking puke.
That right there-- is the part that makes me fucking puke.
That right there-- is the part that makes me fucking puke.
I've never had to kick anyone out of SQL Server in order to do -
ANYTHING-.
I've never had to kick anyone out of SQL Server in order to do -
ANYTHING-.
I've never had to kick anyone out of SQL Server in order to do -
ANYTHING-.
I've never had to kick anyone out of SQL Server in order to do -
ANYTHING-.

Why do you jam 'DOWNTIME' down your users throats?

-Aaron