The Twilight Zone

  • Thread starter Thread starter Stuart
  • Start date Start date
S

Stuart

I have a form with subform. When the subform is in
datasheet mode all is well. However, when it is in
continuous form mode, I enter the MS Access 2002 Twilight
Zone by performing the following steps:
1. Search for a record on the main form using a wizard-
created combo box.
2. Attempt to update the data in any bound control (on
the main form).
This causes Access to blow up and offers to send an error
message to Microsoft. Anyone know why? If it's any
help, this is a .ADP.

Stuart
 
-----Original Message-----
I have a form with subform. When the subform is in
datasheet mode all is well. However, when it is in
continuous form mode, I enter the MS Access 2002 Twilight
Zone by performing the following steps:
1. Search for a record on the main form using a wizard-
created combo box.
2. Attempt to update the data in any bound control (on
the main form).
This causes Access to blow up and offers to send an error
message to Microsoft. Anyone know why? If it's any
help, this is a .ADP.

Stuart
Hi Stuart, just guessing.. you might like to review the
record source of the main form - ensure does not include
same tables/queries as subform - and for the subform -
ensure does not include same tables/queries as main form.

Luck
Jonathan
 
-----Original Message-----

Hi Stuart, just guessing.. you might like to review the
record source of the main form - ensure does not include
same tables/queries as subform - and for the subform -
ensure does not include same tables/queries as main form.

Luck
Jonathan
.
Well, not quite, but almost...

There are actually two subforms. The second one depends
on the record selected in the first one. I use a field
on the main form to load the value from the first one,
and that is the parent property for the second one. If
you understand me...

Not sure this is legal, but it seems to work if both
subforms are datasheets...

Another thing I noticed is that that calculated controls
in the subforms seem to recalculate after every data
change on the main form. Is that normal Access behavior?

Stuart

Stuart
 
Well Stuart, it still sounds to me that there's a good
chance that you have overlapping record source for your
forms.

Luck
Jonathan
 
I've checked pretty carefully, I don't think I do.
The main form is actually quite simple and only sets one
foreign key for the first subform.

Having said that, it works fine when they're displayed as
datasheets, so I will just go with that I guess. More a
matter of curiosity at this point than necessity.

Thanks for your help, Stuart
 
Back
Top