Thread: Unbound fields to table

chigley3, I apologize for my confusion in the previous posts. It is the ControlSource, NOT the SourceObject that you want to put the expression. I re-read one of my previous posts and I'm sorry about getting these mixed up.

If it is easier to use the expression in the query I dont mind. I am trying to put the expression in the criteria box for example =[labour rate]+[labour time] = labour cost the expression is not working in the query? how could something so simple be so complicated?

jeez guys, the response is great! thank you!!

Quote: Originally Posted by chigley3 Please answer the question asked. Since you're new to the forums, I'd suggest having a look at our FAQ . The question has been answered, with many options offered and often with more than adequate information provided. Besides that, I think there are more than a few people around these forums who have qualms with storing calculated fields (it's generally a frowned upon practice).

If it is easier to use the expression in the query I dont mind. I am trying to put the expression in the criteria box for example =[labour rate]+[labour time] = labour cost the expression is not working in the query? how could something so simple be so complicated?

chigley3, I apologize for my confusion in the previous posts. It is the ControlSource, NOT the SourceObject that you want to put the expression. I re-read one of my previous posts and I'm sorry about getting these mixed up.

My Rule is the Table hold the validate less coding needed also when you add a new form showing differance info the validate rule are always there.

On small apps, I use the bound approach and just do the validation in the BeforeUpdate and Cancel it if there is an issue. Other than that I use VBA recordsets (DAO) to write to the appropriate table on SAVE. Code: Sub SaveRecord() <Validation Commands> Dim RS as Recordset Set RS = CurrentDB.OpenRecordSet("<SQL to your Table and Record>") RS.Edit (or RS.AddNew if it's a new record being...

Quote: Originally Posted by klompZA I have a form with unbound fields. Reason for this is so that I can validate the data before writing it to the table. There are few valid reasons for using unbound forms in Access, and the reason you give is certainly not one of them ! I wish a pox on whoever keeps perpetuating this absurd notion! Using unbound forms for data entry means that you are forfeiting at least half of the advantage in using a...

Quote: Originally Posted by klompZA I have a form with unbound fields. Reason for this is so that I can validate the data before writing it to the table. There are few valid reasons for using unbound forms in Access, and the reason you give is certainly not one of them ! I wish a pox on whoever keeps perpetuating this absurd notion! Using unbound forms for data entry means that you are forfeiting at least half of the advantage in using a...