In a well designed relational database, you do not duplicate data. it leads to errors. Calculated fields are on Richard's Evil Access Stuff

So instead of a Field for FirstName and LastName you'd want just one for FullName instead?

That makes it more difficult for searching/sorting.
Also how do you handle MiddleName, spaces in names etc?

@ Alex Hedley... not quite...

I've created a Field that concatenates [LastName] & ", " [FirstName] as a field named [FullName] in the CustomerT itself.

This way, I am not concatenating these two fields on every Query I use on every form. I simply refer to the [FullName] field rather than concatenating these two fields on every query, time and again.

I was asking why not do this at the table level rather than the query level.

As for [MiddleI], that can be included or not as one see fit.

Experience have proven that Calculated fields in table can cause issues. That is why Calculated fields are on Richard's Evil Access Stuff

Why not just create a base Query that contains the shared info you need on every form, you can always create another query off that if you need other fields.

Thank you gentlemen... please put away your cannons... I was asking a simple question which Sami answered on the first response.

I understand the redundant info issue.
I further understand, Alex, about putting it in a query; and creating a base query to base a new query off of.

Thank you again!

In the extended cut video of Calculated Fields, made in 2021, Richard actually said he was unsure if it was good or bad to use calculated fields in tables, and he was going to "look into it" further.  I don't know if his opinion has changed since then or not.

I'm fairly old-school so I avoid using calculated fields in tables.  I prefer having all calculations done in coding environments (modules, forms, reports, etc.).

Thanks for your input Kevin!

I appreciate all of you for your willingness to correctly advise me!

I am on a journey to become a Developer in order to develop an application for which I have already obtained a copyright.

I am certain that I will need much advice as I travel this path and I am certainly glad that I have a forum to consult of more experienced Developers than I!

Richard has a new video on this coming soon.

Mark,

We all walked that path. All of us are still learning.