First Name / Last Name

[RickRusty]

Most CRM's create 1 field for a contact name.

Is that NOT a good plan with Access?

If it's OK. How does it SORT or Search?

 

[Isskint]

Hi Rusty,

Personally i would say not. I generally supply FirstNames and Surname fields. For display purposes concatenate them, EG Surname, Firstnames. Users have the option to sort on either name.

I have gone with a single field a couple of times, but in those instances i provide a form for inputting names and have the user type FirstName(s) and Surname and then concatenate them in a set format for the Name field. If you go down this route, i would suggest storing as Surname, Firstnames, as this makes sorting slightly more 'useful'.

 

[pbaldy]

I agree. It's generally easier to store the components separately and concatenate them as needed than to store them together and try to break them apart when you just need one part.

 

[RustyRick]

SOLVED

Thanks guys for the advice. I'll stick with it.

I also use ACT and they have the 1 field thing working pretty good.

 

[CJ_London]

Most CRM's create 1 field for a contact name.

not in my experience, most (good) CRM's will have several fields e.g.

Title
Forename(s)
Middle Initial(s)
Surname
Honours
Salutation

Depending on requirements you may not need all these fields.

you search on one or more fields as you would for anything else. How it is expected you will search/sort will be part of the decision as to which fields you need.

 

[RustyRick]

I've wondered about that for decades. But ACT does a nice job of it.