Form Subform calculated field works only when it "feels like it"

[jree3000]

Hi. I have a form that has a field that is used to show a calculated field from a subform. Sometimes it works like it is supposed to but more often than not I get a "#Name? error". I'm baffled as to why it works sometimes but not others. Haven't been able to make rhyme or reason of it.

The subform is used to show items ordered. It has a calculated field in the form footer called "subtotal". The subtotal sums the subform field named '"DosePrice" by using the following control source "=Sum([DosePrice])". Both the DosePrice field and the subform field are currency fields.



The subform name within the form is "Tracker_Subform". The field within the main form is called "GrandTotal" (also a currency field). The control source for GrandTotal is "=[Tracker_Subform].[Form]![subtotal]"

So as I have stated it will sometimes work properly but more often than not I get the #Name? error. Anyone have any experience with these type of issues? I'm really at my wits end trying to figure this out. Thanks in advance!

[ranman256]

I too see this. Have you tried on the main form ON CURRENT event to refresh it?
GrandTotal.Requery

Its possible the subform hasnt finished adding yet when main form can show its value.
or conversly, update the mainform.grantotal from the subform.

[Missinglinq]

Is DosePrice an entered value or is it, too, a calculated field?

Linq ;0)>

[jree3000]

Missinglinq, DosePrice is an entered value.

However I think ranman256's suggestion fixed it! It appears to be working properly now. Thank you!

[Missinglinq]

Is DosePrice an entered value or is it, too, a calculated field?

Also, although we usually think of Forms or entire Databases when we speak of corruption, individual Controls can and do become corrupted. The test and the fix are one and the same; deleting the Control then re-creating it! If it was corrupt, you've verified the fact and solved the problem! Because of the 'sometimes it works, sometimes it doesn't' aspect of the problem, this is a real possibility, so I'd do the above to the calculated Control on the Subform, and if that doesn't solve it, do the same to the Control on the Main Form.

Linq ;0)>