Kacy-
Ah, the problem is you've defined the Project field as Multi-Value. NEVER do that - it's a terrible feature in Access. You will get one record per related project, and the Multi-Value field lets you associate multiple projects. To properly reflect a many-to-many relationship (on project can have many needs, and a need can be related to many projects), you should have a "linking" table. Your table structure should look like:
Projects:
ProjectID (PKey), ProjectDesc, etc…
Needs:
NeedID (PKey), NeedDesc, etc…
ProjectNeeds:
ProjectID (PKey 1), NeedID (PKey 2), etc… (perhaps include need priority for this project)
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Oct 22, 2015, at 5:49 PM, theaterkacy <no_reply@yahoogroups.com> wrote:
I am also starting to see the duplicate records in a related form (based only on one table, but with a relationship to the Project IDs). Is it possible to apply a group to the form to eliminate the duplicates there?
Here is the record source for the form:
SELECT [Needs and Recommendations].*, [Needs and Recommendations].Project.Value
FROM [Needs and Recommendations]
Here is the record source for the form:
SELECT [Needs and Recommendations].*, [Needs and Recommendations].Project.Value
FROM [Needs and Recommendations]
__._,_.___
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (6) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar