Hi Evan ---

I second what Michel and Erik have posted. But, generally, I try to stick with simple in-line functions to calculate the fullname as required where a view might be overkill, i.e., some reports, forms, et al. One of the problems with always using a cursor is view is that the user might expect to be able to directly edit an aggregate fullname field.....perception kills :-)



>How does everyone else manage the firstname and lastname fields in a database?
>
>Do you create a third field called name which is updated by an update trigger?
>
>person.lastname = "Delay"
>person.firstname = "Evan"
>person.name = "Delay, Evan" (trigger fills in??)
>
>I find that I am constantly combining the first and last name together to present to the user or for indexes..etc..
>
>Or do you use a function or a class...?