Concatenate name fields

[DeanLinCPR]

I have a 2007 DB with first and last name fields. I am trying to merge them
in a common field I know it is unusual. I have created a select query that
works but I cannot get to update the table

SELECT [MembershipAndData]![FirstName] & " " &
[MembershipAndData]![LastName] AS [MemberName]
FROM MembershipAndData;

Any hellp would be appreciated

 

[BruceM via AccessMonster.com]

Don't add them to the table. Combine them just as you have done, so they
will display as you wish when you need it. There is rarely a need to store a
calculated field. In any case, a select query only displays data. To add to
a table field you could use an update query, but again you should not. For
one thing, if a name changes you only need to change it in one place. If you
store the combined names you need to change it in two places.

I have a 2007 DB with first and last name fields. I am trying to merge them
in a common field I know it is unusual. I have created a select query that
works but I cannot get to update the table

SELECT [MembershipAndData]![FirstName] & " " &
[MembershipAndData]![LastName] AS [MemberName]
FROM MembershipAndData;

Any hellp would be appreciated

 

[John W. Vinson]

I have a 2007 DB with first and last name fields. I am trying to merge them
in a common field I know it is unusual. I have created a select query that
works but I cannot get to update the table

SELECT [MembershipAndData]![FirstName] & " " &
[MembershipAndData]![LastName] AS [MemberName]
FROM MembershipAndData;

Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.

Just redo the calculation whenever you need it, as a
calculated field in a Query just as you're now doing it. The calculated field
can be used in a Form or Report, it can be exported, it can be used for
sorting or searching, or for anything that you could use a table field
(anything but editing, which you would generally NOT want to do).

If you have some special reason for violating the rules in this way please
post back and explain.