I guess I misstated the field. Yes, the "Number to Order" field in the query works properly, it's the "Number Needed" field in the "Main" form which does not. Sorry for the confusion.
I guess I misstated the field. Yes, the "Number to Order" field in the query works properly, it's the "Number Needed" field in the "Main" form which does not. Sorry for the confusion.
I sure would think that is plenty of machine to run this ap properly. How about my post #14?
I take it the "Number to Order" FORM bound to the "Number to Order" query works properly then.
Yes, however it is a datasheet form, which you probably noticed. Don't know whether that makes much of a difference?
How about modifying the "MainQuery" to include the calculations and then use that query for the Main Form instead of the table? If that works then as I said, I think this is simply some sort of "Access" timing issue.
Not sure how to do that since, when I pull up the field list from the "Add existing fields" button for the "Main" form, it only gives me fields from tables to choose from and not querys.
On the Data tab of the property sheet for the Form is a Record Source property (1st line). That is where you select the query instead of the table.
Success, thank you RuralGuy for your help!
Great! The formula in the control gave you an error but putting the calculation in the RecordSource of the form works as expected, right?
That is correct
It has to be some sort of Access timing issue. Glad we came up with a solution that works. Again, put as many of the calculations in the RecordSource query and if you change values it will update the form as well.