G
Guest
I have a sub form that is displayed as a Continuous Form. I have a one to
many relationship between the main forms records and the sub form.
My application allows the user to select a record on the main form, the sub
form gathers all matching sub form records and displays them, with some
calculations.
The problem I am having seems to have to do with timing. I have several
summary fields on the sub forms, that rely on one another that I am getting
INTERMITTENT errors on. I have been trying to figure out the cause and am
substantially sure that this is the case. As the form is loaded and the
values are filled into the controls sometimes access is trying to assign
values based on fields that have note finished calculating yet. SO, even
though all of the values appear on the form, some of the final total fields
that rely on other fields end op with "Error" displayed.
My questions . . . What would be an elegant solution to this problem? I
TRIED adding a control.requery to the afterupdate event of the fields that I
am "waiting" on. Didn't seem to help.
The problem is NOT consistent. As I move from record to record making not
of where this occurs if I return to a "problem record" the problem usually
goes away.
In case it makes a difference I am using Access 97
many relationship between the main forms records and the sub form.
My application allows the user to select a record on the main form, the sub
form gathers all matching sub form records and displays them, with some
calculations.
The problem I am having seems to have to do with timing. I have several
summary fields on the sub forms, that rely on one another that I am getting
INTERMITTENT errors on. I have been trying to figure out the cause and am
substantially sure that this is the case. As the form is loaded and the
values are filled into the controls sometimes access is trying to assign
values based on fields that have note finished calculating yet. SO, even
though all of the values appear on the form, some of the final total fields
that rely on other fields end op with "Error" displayed.
My questions . . . What would be an elegant solution to this problem? I
TRIED adding a control.requery to the afterupdate event of the fields that I
am "waiting" on. Didn't seem to help.
The problem is NOT consistent. As I move from record to record making not
of where this occurs if I return to a "problem record" the problem usually
goes away.
In case it makes a difference I am using Access 97