This is clearly a newbie question, right? I just haven't been able to work this out:

In setting up a form, I have created some calculation controls and concatonation controls, such as total, and a custom date code. And I want to write the calculated values into fields in the record. I'll use "Total" as an example:

I've got a control in a form called "Total" that uses a formula in its "Control Source" property to calculate a total. The form beautifully calculates the total after every change. Now I want to save that value into the record, in a field called "Total".

What's the easiest way to save the value of a calculation control to a field in the current record?

Thanks, I've been on this for hours.

Welcome to Utter Access.
Do not save a calculated value to a table. You should calculate the value on the fly as needed.

Welcome to Utter Access

just as Truitt said... Do not store calculated values -- that is the beauty of them -- they can be calculated anytime. Storing them risks the integrity of your data.

Just as you can make the total show up beautifully on a form, you can do the same on reports.

OK, so saving "totals" may not be a good idea.

But I do want to save a concantonated custom code from the date something like this: = UserID & yymmdd & SubNumber. As before, the control is working great.

This one I'd really like to store in the record. Is there a "preferred method" for storing calculations in a record?

Thanks,

Kevin

instead of making the equation the ControlSource, the ControlSource of the custom code should be your fieldname. To calculate it, create a function behind the form



on the AfterUpdate Event of UserID and SubNumber

=MakeCode()

Thanks. This looks great.

you're welcome (IMG:http://www.utteraccess.com/forum/style_emoticons/default/wink.gif)

just out of curiosity ... what is the purpose of this custom code?

Thanks again.
The below code worked, after tweaking and customizing. The purpose of this is to generate a PO number, made up of user ititials, date, and a sub-number. Looks like this:

KL-050622-1

<<

Private Function MakeCode()
Me!PurchaseOrderNumber = Null
If IsNull(Me.EmployeeID) Then
strMsg = "You must pick a value from the Employee ID list."
strTitle = "Employee ID Required"
intStyle = vbOKOnly
MsgBox strMsg, intStyle, strTitle
Cancel = True
End
End If
If IsNull(Me.ordersubnumber) Then End
Me!PurchaseOrderNumber = Me.EmployeeID & "-" & Format(OrderDate, "yymmdd") & "-" & Me.ordersubnumber
End Function

>>

As previously advised you should NOT be storing calculated values. There is no need for it since you can use the same expression to display the value whenever needed. You are storing the EmployeeID, the order date and the subnumber. Why waste an extra field on the PO Number? Whereever you need to display the PO Number, be it on forms, reports or in queries just use the expression:

= EmployeeID & "-" & Format(OrderDate, "yymmdd") & "-" & ordersubnumber