>That is exactly what I have. The problem comes in when moving through the
>records on the subform; the next record will change the first records txt
[quoted text clipped - 11 lines]
>> in the subform(?) Current event in addition to each
>> individual control's AfterUpdate event.
No it is not a continous form. The view is "form" view", each tab is a
different section pertaining to the case associated with the member info on
the main form. A member can have mulitple cases that is why the subform
(tab's) has multiple records associated with it. However the view is not
datasheet or a continues form.
> Are you saying the subform is in continuous view?
>
[quoted text clipped - 20 lines]
> >> in the subform(?) Current event in addition to each
> >> individual control's AfterUpdate event.
missinglinq - 14 Jul 2007 18:02 GMT
I'm confuse! If the subform's records aren't being shown datasheet or
continuous how do you know what record B is doing to the controls on record A?
>No it is not a continous form. The view is "form" view", each tab is a
>different section pertaining to the case associated with the member info on
[quoted text clipped - 7 lines]
>> >> in the subform(?) Current event in addition to each
>> >> individual control's AfterUpdate event.

Signature
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Marshall Barton - 14 Jul 2007 18:43 GMT
Then it sounds like you might have a problem coordinating
the multiple subforms. You might(?) be able to overcome at
least part of this problem if you don't enable/disable all
the subforms from the main form and use each subform's
Current event instead ( and possibly the tab control's
Change event.

Signature
Marsh
MVP [MS Access]
>No it is not a continous form. The view is "form" view", each tab is a
>different section pertaining to the case associated with the member info on
[quoted text clipped - 11 lines]
>> menu) on each of the controls that you want to
>> enable/disable.