"Supe" <(E-Mail Removed)> wrote
> Can a Field be made in a table that will concantenate
> two other fields in that same table?
You cannot define a Field in a Table to be a concatenation of anything --
that would be, in relational DB terms, trying to "commit spreadsheet". A
database is not just a bigger version of a spreadsheet. You can set the
value of a Field with a calculation in a Query, but all you store is the
result, and you'd have to rerun the Query if one of the Factor Fields were
changed.
As Rick has pointed out, that would be redundant storage of information. In
these days of inexpensive storage, the extra cost of the storage is not a
big deal, but the need for those recalculations certainly could be. My
experience is that it is not a matter of IF, but how soon the factors and
the result will not match and then you will have to determine which is
correct.
If you intend, as you say, to use a Query to compare a concatenation of two
Fields, you can, as easily, either compare the two Fields individually, or
include a calculated Field in the Query that concatenates them. The latter
is the "relational database way" -- don't store duplicated or redundant
data, and calculate values when you need them (even if the 'calculation' is
just a concatenation).
Larry Linson
Microsoft Access MVP
|