By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,412 Members | 2,882 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,412 IT Pros & Developers. It's quick & easy.

"Access needs to close" when refreshing a form in Acc2002 but not in 2000

P: n/a
J
Hi,
Ive got 3 forms, (a subform within a subform within a form) and when I
refresh the outermost form, Access closes and offers to send an error
report.

The forms worked fine a few weeks ago, but now they cause this error
in Access 2002 (Access 2000 is fine)

Each of the sub forms use values from their parent forms to produce
results.

There isn't a problem loading the forms in the first place; the
problem only occurs when you refresh the outermost form(using either
the menubar or F9).

Each if the forms work fine independantly, and it is only when all 3
forms are present that the problem occurs.

Someone has suggested to me that it may be due to a number of windows
updates that have been done in the last few week.

I have tried installing Office XP SP3, but this has no effect. I can
supply more details about the forms in question if necessary, but I
think that this may be more to do with a difference between 2000/2002
than with the forms themselves.

I have tried compacting and repairing both "sides" of the database:
the data tables are stored on the server and accessed via the
"frontend" database on individual user's machines.

Can anyone think of what may be causing this problem?

TIA
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
J, here are a couple of things to try:

1. Turn off the Name AutoCorrect check boxes under:
Tools | Options | General
Then compact the database:
Tools | Database Utilties | Compact.
For an explanation of why, see:
http://allenbrowne.com/bug-03.html

2. In each subform, add a (hidden) text box for the foreign key field(s).
This sounds really daft, but try it and see if it makes a difference.
Although Access should be able to cope with referring to the member of the
Fields collection in the subform, if you actually create a control so it can
use the Controls collection instead, it can prevent Access 2002 and 2003
from crashing.

3. Check the names of your controls. Access typically uses the same Name for
a control as its ControlSource, and that works okay. But if you alter the
ControlSource *without* altering the Name, you can confuse Access and
trigger bugs that are difficult to trace.

These issues are especially important for the fields names in the
LinkMasterFields/LinkChildFields properties of the subform control. As well,
make sure that none of these fields has a name that matches anything else
such as Name (forms have a Name property) or Section (forms have sections).

--
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.

"J" <a@lawhead.fsnet.co.uk> wrote in message
news:b3**************************@posting.google.c om...

Ive got 3 forms, (a subform within a subform within a form) and when I
refresh the outermost form, Access closes and offers to send an error
report.

The forms worked fine a few weeks ago, but now they cause this error
in Access 2002 (Access 2000 is fine)

Each of the sub forms use values from their parent forms to produce
results.

There isn't a problem loading the forms in the first place; the
problem only occurs when you refresh the outermost form(using either
the menubar or F9).

Each if the forms work fine independantly, and it is only when all 3
forms are present that the problem occurs.

Someone has suggested to me that it may be due to a number of windows
updates that have been done in the last few week.

I have tried installing Office XP SP3, but this has no effect. I can
supply more details about the forms in question if necessary, but I
think that this may be more to do with a difference between 2000/2002
than with the forms themselves.

I have tried compacting and repairing both "sides" of the database:
the data tables are stored on the server and accessed via the
"frontend" database on individual user's machines.

Can anyone think of what may be causing this problem?

TIA

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.