okay. what goal are you trying to achieve with a requery of the subform as
you move from one record to another in the main form?
The problem occurs when new values are calculated for the subform. Even
though the subform is requeried in code, as described above, the continuous
subform in question displays one record with "#error" in one of the controls.
When I put my cursor in the subform and hit "Shift+F9", the subform
requeries properly and displays the data correctly.
>okay. what goal are you trying to achieve with a requery of the subform as
>you move from one record to another in the main form?
[quoted text clipped - 4 lines]
>> >>
>> >> Bill

Signature
Bill Reed
"If you can't laugh at yoursel, laugh at somebody else"
tina - 24 Jan 2006 21:04 GMT
well, when a mainform/subform are linked properly, the subform is
essentially "requeried" each time the user navigates to a different record
in the main form, so i don't really understand why an additional requery is
needed at all. but be that as it may, it's strange that only one record in a
continuous form would show an error in a calculated control that "fixes"
itself on a requery of the subform. you've got me stumped, Bill, sorry i
wasn't able to help.
> The problem occurs when new values are calculated for the subform. Even
> though the subform is requeried in code, as described above, the continuous
[quoted text clipped - 10 lines]
> >> >>
> >> >> Bill
Bill R - 24 Jan 2006 21:08 GMT
Thanks for your effort
Bill
>well, when a mainform/subform are linked properly, the subform is
>essentially "requeried" each time the user navigates to a different record
[quoted text clipped - 9 lines]
>> >> >>
>> >> >> Bill

Signature
Bill Reed
"If you can't laugh at yoursel, laugh at somebody else"