Check the name of the control. It must be DIFFERENT from the name of ANY bound field. Sometimes people drag a field from the list so it starts out bound. Access usually gives bound controls the same name as the field to which they are bound. If you later change the control to be unbound, you MUST remember to change the control name.
Steve,
You may have elected to take Jeffery's suggestion to move the concatenation to a query but I believe I did identify the problem which was that the name of the control caused a conflict.
I see that you are using "txt" as the prefix so I'm going to assume that you are referencing control names rather than field names. Try using field names. You can get sometimes away with using control names as long as the controls are in the same section as the reference. The point is that what you are doing is valid but there is a syntax error somewhere and without seeing the database, I took a shot at it being a name conflict since that is the most common error. I normally concatenate and calculate in the query myself so I do what Jeffery suggested but what you did should work once the "syntax" error is corrected.
As long as you are happy with the solution, that's fine but for purposes of understanding, I don't want you to be afraid to ever do this again since there is no technical problem with your original solution. It is "syntax".
Yes, review what Pat suggested.
90% of the time, ...it is a naming issue.
I have no problems with a points split....
Microsoft Access
Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.