I have a form with several fields for basic customer information. On the after update procediure i have a query run to concatenate the first name and last name fields into one field of all records. I was wondering if this would create problems later on if multiple people are using the database and records are updated. would it corrupt any client data? should i be concerned about this?

Why the update query place something like Full Name:([Fname])&" "&([Lname]) then use Full Name as the Control source in your Form etc. Sorry I did not answer your question to the best of my knowledge it will not corrupt anything.

Edited by: jmcwk on Fri Aug 25 18:24:50 EDT 2006.

i know i can use the fullname as a control source, instead of using a query, but i needed the full name field elsewhere in the database and instead of writing :([Fname])&" "&([Lname]) on reports, other forms, etc, i thought of using the update query, then i could just use the fullname field.

Col,

Just adding to John's post. If you properly split your application into multiple 'front-end' copies that each work-
station will have, and 1 main back-end that is linked to all the front-end's you should be ok.

Just my 2 1/2 cents worth.

Aqua

Col,

As to the:

"but i needed the full name field elsewhere in the database and instead of writing [Fname])&" "&([Lname]) on reports, other forms, etc,"

Why write more code to get the same job done?
Just my opinion.

Aqua

You are the Developer that was just my opinion, to me you are creating more cause for possible errors using the Updates as opposed to a Static Control Source as well as the fact to me more work. Not critisizing your approach or reasoning thats just my opinion.

Aqua, my intent was to split the db later. but in the testing/building phase i havent done it yet.

john: i see your point. concatinating the field in a control source may be a better method. thanks.

the reason i asked if running an update query would cause problems, was because i ran an update query and it corrupted a record. it turned some data into chinese characters. i need to make sure this doesnt happen later when the db goes live.

This is exactly what you *should* do. Storing the Full Name would be storing a calculated field. This is not proper DB design. You can always derive the Full Name from the FirstName and LastName fields with a simple expression like you have posted.