Field value from expression

[MLD]

Win XP/Acc03

Is it possible at the table level to derive the default value of a field
from a concatenating expression of two other fields? Basically I want the
FullName field to auto-populate as LastName,FirstName { actual expresion
used '=[LastName]&","&[FirstName' }. I tried using this in the Default Value
property, the Valdiation property etc, to no avail.

Yes, I know I can do it ina query and rewind to a lookup, but I'd like to
keep it simpler with less objects and less chance for cyclical error.

Unless what I'm trying to do IS a cyclical error in itself? Does this have
to do with the fact that the record isn't saved while entering, so the field
can't update on the others?

Thanks,
-Monica

 

[Rick B]

At the table level? No.

That would be redundent to store the data in the table in more than one way.

To get a calcualted value like that, do it in your query, report, or form.

The table should only have unique data.

 

[Rick B]

Forgot to mention....

There is no need for your "FULL NAME" field. You should remove it from your
table and stick to the LastName and FirstName fields.

 

[MLD]

The "need" is not mine, it is desired by the original designer of the base
who wants to keep certain information as is.
I know its redundant, you know its redudant, but I just work here and do as
I'm asked.
Relax a little - quit trying to be Design Gustapo. People have weird reasons
for programming what they do.

Forgot to mention....

There is no need for your "FULL NAME" field. You should remove it from your
table and stick to the LastName and FirstName fields.


--
Rick B

Win XP/Acc03

Is it possible at the table level to derive the default value of a field
from a concatenating expression of two other fields? Basically I want the
FullName field to auto-populate as LastName,FirstName { actual expresion
used '=[LastName]&","&[FirstName' }. I tried using this in the Default Value
property, the Valdiation property etc, to no avail.

Yes, I know I can do it ina query and rewind to a lookup, but I'd like to
keep it simpler with less objects and less chance for cyclical error.

Unless what I'm trying to do IS a cyclical error in itself? Does this have
to do with the fact that the record isn't saved while entering, so the field
can't update on the others?

Thanks,
-Monica