Karen,
Having nasty redundancy like that is an invitation to troubles down the road.
Much better to merge the fields with a well thought out function, when necessary, then to have the possibility that some data entry clerk changes a name field, but not the merged name field. In that case, which field value would you trust when looking at the data?
Another option would use a
VIEW to present the merged field as part of a "virtual table".
But, as much as possible, please, please, please stick to the database normal forms. You'll appreciate it. See
this wiki link for a discussion of normal forms, and why they're a GOOD THING.
Luck!