How to let my combo list selection appear in full in my table

[Micron]

I'm surprised that nothing was said about spaces and special characters in names ( / ) or using reserved words as names (e.g. Date).

[Minty]

I'm surprised that nothing was said about spaces and special characters in names ( / ) or using reserved words as names (e.g. Date).

Baby steps...

[Micron]

That IS a baby step. Proper design precedes everything - at least IMO.

[Minty]

That IS a baby step. Proper design precedes everything - at least IMO.

I agree, but suspect the suggested use of the FK in the child table is not being used.
Happy for the OP to prove me wrong.

[ssanfu]

And maybe a mention that ALL CAPS IS EQUIVALENT TO SHOUTING??

[Micron]

And maybe a mention that ALL CAPS IS EQUIVALENT TO SHOUTING??

You're referring to post #1? Maybe that's just an accurate representation of the actual field names.

[Emmanuel]

@Minty
If I may ask...
What will happen if I happen to store the full name in the income table?

[ssanfu]

@ Micron,
Actually, I was looking at the dB posted by the OP. All of the field names were caps.... As were the objects in the Nav pane.....my eyes are still tired. (maybe it is just me being picky)

[Micron]

Maybe that format just looks good on a form or report. Sure would be easier than re-typing all the labels but the object names might be a bit much. As long as it's not all caps in a post I wouldn't object.

Yeah, I think you might just in a foul mood like I am lately. The elevator is often stopped in the basement if you get my drift.

[Minty]

@Minty
If I may ask...
What will happen if I happen to store the full name in the income table?

Well the world won't stop turning, so this is all just best practice.

Let's assume Mary Smith has lots of records. She is stored as

MemberID	Fname	Lname
2	Mary	Smith

She is stored in the Name version of your table as

Income_ID	MemberName
375	Mary Smith
376	Mary Smith

Mary get married and is now called Mary Jones

In the name version you have to change her name in the member table and also every record in the income table that she has.

If it was stored as

Income_ID	MemberID_FK
375	2
376	2

You only change the name once in the member table and all the forms, and reports are magically correct, no alteration of any of you other data where that member is referenced is required.

Also by storing the full name in the second table you have to join on both FName and LName fields to be able to look up any other member information, which isn't ideal.

This also applies if a simple typo was made in the name.
By storing it everywhere you have to ensure you update it everywhere.

[Emmanuel]

@Minty
Very well explained
I get your arguments now

[Welshgasman]

@Minty
Very well explained
I get your arguments now

Obviously, I need to do better?

[Emmanuel]

@ Welshgasman
You did great too
I do appreciate

[Welshgasman]

@ Welshgasman
You did great too
I do appreciate

Not really. I said or tried to say the same thing, but the message did not get through.?
I tend to try an stimulate a spark in the O/P that makes the O/P think 'Ah I see now'

Missed it in this case?

[Emmanuel]

@ Welshgasman
No worries buddy
What matters most is that we’ve got each other’s back👍🏽