Toukey,
Please respond in a way that includes the previous email thread so we don't have to look back through deleted emails to get a sense of what you are referring to.
No one can give you good advice about tables without understanding the purpose of your application. Many of us old mature developers will step away from the computer when designing our table structure. Make sure you have an eraser to fine tune your tables.
Our very own Crystal has an excellent resource for the basics at http://www.accessmvp.com/strive4peace/.
Microsoft Access Basics on GoSkills 40 lessons to empower you to build an application with Access Access Basics is designed for those of you with a thirst to understand the fundamentals of Access with programming in mind ... whether you realize it or not. www.accessmvp.com |
Duane
From: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io> on behalf of toukey1 via groups.io <toukey1=yahoo.com@groups.io>
Sent: Thursday, April 30, 2020 8:33 AM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: Re: [MSAccessProfessionals] Getting duplicate values in combo box
Sent: Thursday, April 30, 2020 8:33 AM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: Re: [MSAccessProfessionals] Getting duplicate values in combo box
Thanks for your response Duane.
So then I should have 2 tables; one with the client info as you have in your response and the other would hold the recdate e.g. recdateid (primary key) recdate and ClientID (from the client table) where the join would be on the ClientID in both tables?
Regards
Toukey
So then I should have 2 tables; one with the client info as you have in your response and the other would hold the recdate e.g. recdateid (primary key) recdate and ClientID (from the client table) where the join would be on the ClientID in both tables?
Regards
Toukey
Tidak ada komentar:
Posting Komentar