application quits

[Danifrog]

I have a form with a subform and a few buttons that open various
reports, tables and forms. Sometimes when I open it in any view or try
and save it, the application quits. It does this quickly without
saving any design changes and without closing the .Ibd files. There
are no error messages either. I have tried decompiling, compacting,
transferring all objects to a new database file and even recreating the
entire form from scratch. The problem does not happen every time and I
can go a week or so without any problems.

Any ideas what this might be or how t go about finding out?

DAG

[Allen Browne]

If you have not yet turned Name AutoCorrect off, it is most likely
corrupting your database. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
More info:
http://allenbrowne.com/bug-03.html
Then compact again.

If this is Access 2002 or 2003, try adding a text box to the subform for the
field named in the LinkMasterFields property of the subform control. Known
issue.

If the RecordSource of the main form or subform contains a subquery, try
removing the subquery to see if the crash stops. If it does, look for an
alternative to the subquery (such as stacking one query on another.)

Also worth checking the service pack for your version of Office and also
your version of JET 4:
http://support.microsoft.com/gp/sp

More general suggestions:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Danifrog" <gi*****@crestedbutte.net> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I have a form with a subform and a few buttons that open various
reports, tables and forms. Sometimes when I open it in any view or try
and save it, the application quits. It does this quickly without
saving any design changes and without closing the .Ibd files. There
are no error messages either. I have tried decompiling, compacting,
transferring all objects to a new database file and even recreating the
entire form from scratch. The problem does not happen every time and I
can go a week or so without any problems.

Any ideas what this might be or how t go about finding out?

DAG

[Danifrog]

Thanks! I did what you suggested, read through your suggestions. I
can't tell for sure because it doesn't happen every time but hopefully
this solved it.

Debbie

[Danifrog]

Oops, spoke too soon. I compacted, decompiled, compated again,
compiled and still the application quit unexpectedly without an error
msg!

Debbie

[Danifrog]

Also I transferred all objects to a new db file. Still quit on me!

[Allen Browne]

What version of Access is this?
Locate msaccess.exe, typically in c:\program files\Microsoft Office\Office.
Right-click it and choose Properties.
What version?

What version of JET are you running?
Locate msjet40.dll, typically in \windows\system32.

What References are checked?
Open a code window in Access.
Choose References from the Tools menu.
Which ones have a checked box?

Does this happen with just one form (and its subform)?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Danifrog" <gi*****@crestedbutte.net> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

Also I transferred all objects to a new db file. Still quit on me!

[Danifrog]

Access 2000

Jet 4.0.8618.0

References:
Visual Basic For Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX DataObjects 2.1 Library
Microsoft DAO 3.6 Object Library
Microsoft Excel 9.0 Object Library

This was happening with just one form. I recreated just part of this
form from scratch (everything except the subform) and now it is
happening with this new form as well.

Thanks for your help.

Debbie

[Allen Browne]

You have narrowed it down a little, in that the simplified main form still
shows the problem, so it's not the subform.

Check under Help | About that you have "SP3" for Office 2000.

You may be able ot move the OLE Automation and ActiveX DataObjects
libraries. Does it still compile? If so, you have simplied it down further.

Presumably Name AutoCorrect is still off.

Now to this new form. What is its RecordSource? Table? Query? What's in the
query? Are these local Access tables, or attached Access table, or attached
ODBC tables, or ...?

Any combos or list boxes on this form? What is their RowSource?

When does the crash occur? When you start to edit a record? When it goes to
save a record? When you click a button?

Do all modules use Option Explicit? If not, add it and compile again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Danifrog" <gi*****@crestedbutte.net> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

Access 2000

Jet 4.0.8618.0

References:
Visual Basic For Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX DataObjects 2.1 Library
Microsoft DAO 3.6 Object Library
Microsoft Excel 9.0 Object Library

This was happening with just one form. I recreated just part of this
form from scratch (everything except the subform) and now it is
happening with this new form as well.

Thanks for your help.

Debbie

[Danifrog]

I have SP3.

I removed all unused references.

Name AutoCorrect is off.

Recordsource for the form is a query based on linked tables.

Row source for combo boxes are linked tables.

All modules use Option Explicit.

I can often get it to crash by opening the form in design view and then
changing to form view. Usually I have to do this numerous times in
order to get it to fail.

It may also fail when saving changes in design view or by simply
opening it.

Is there anything that might make it fail from just changing the view
or saving or opening the form?

In the meantime I have been working on deleting things from the form
one at a time and testing it.

Thanks for your help, I have at least been able to clean up a few other
things.

Debbie

[Allen Browne]

Okay, you've got most things tied down.

If it fails when you load the form, then the first place to look will be the
code that executes at that point. This includes Form_Open, Form_Load,
Form_Current (especially) of the main form, and the same events of the
subform. It could also be the GotFocus or Enter events of the first control
in the tab order on the form (and on the subform).

Another option is to decompile. You do that 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"
Then compact, and compile again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Danifrog" <gi*****@crestedbutte.net> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

I have SP3.

I removed all unused references.

Name AutoCorrect is off.

Recordsource for the form is a query based on linked tables.

Row source for combo boxes are linked tables.

All modules use Option Explicit.

I can often get it to crash by opening the form in design view and then
changing to form view. Usually I have to do this numerous times in
order to get it to fail.

It may also fail when saving changes in design view or by simply
opening it.

Is there anything that might make it fail from just changing the view
or saving or opening the form?

In the meantime I have been working on deleting things from the form
one at a time and testing it.

Thanks for your help, I have at least been able to clean up a few other
things.

Debbie