Form with subform suddenly causing Access to crash

[George Avery]

If anybody can tell me what might be causing my problem, I'd be very
grateful.

We have an Access front end to a SQL back end. It's been working without
any problems but has recently started to crash whenever one of the forms
is opened. The form is a main form with staff member details which has a
tab control on it with several tabs most of which contain a subform with
data related to the staff member via the staff record id (an autonumber
field) on both the parent and child.

I have tried creating a new form and putting one of the sub forms onto it
and get the same behaviour. MSAccess crashes and looking at the error
report, it seems to tell me that MSAccess.exe was the application and
MSJet40.dll was the cause.

Where should I start looking in my efforts to solve this please?

 

[Jerry Whittle]

Almost certainly that form, or one of the subforms, is corrupt. Try creating
a new database file and importing all objects into it. First do the tables,
queries, reports, macros, then modules. Next import the forms not giving you
problems. Lastly import the problem form and subforms one at a time. If some
do not import, they are corrupt. You'll need to rebuild them from scratch or,
hopefully, you have a good, recent backup and can import them from it.

You may need to set up all the security and relationships plus startup
options in the new database.

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[GA]

If anybody can tell me what might be causing my problem, I'd be very
grateful.

We have an Access front end to a SQL back end. It's been working without
any problems but has recently started to crash whenever one of the forms
is opened. The form is a main form with staff member details which has a
tab control on it with several tabs most of which contain a subform with
data related to the staff member via the staff record id (an autonumber
field) on both the parent and child.

I have tried creating a new form and putting one of the sub forms onto it
and get the same behaviour. MSAccess crashes and looking at the error
report, it seems to tell me that MSAccess.exe was the application and
MSJet40.dll was the cause.

Where should I start looking in my efforts to solve this please?

After posting this item whilst in the office, I had a few minutes to
spare before I left for home so I had one more try and bingo it
worked, I've got absolutely no idea why though.

My form was based directly on a linked table. I changed the source to
a select query and just included all the fields in the source linked
table.

I've reproduced both the fault and the solution (after compiling the
front end and deploying it) on 4 other work stations.

For the sake of my sanity - I'd love to know why this happened and why
why the change solved the problem.

GA

 

[Ed Warren]

I have seen a similar problem if the field in the SQL database is a date
field and is outside the 'acceptable' (ODBC, MS Access Limits) , eg.
improperly entered ( 01/01/089) or some other stupid thing (should have been
caught with the validator, but 'real men don't always validate' ;(

Other than that ???

Ed Warren.