Personally, I wouldn't use multi-value fields. I much prefer the control I have over normalized tables.
Regards,
Duane
From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com> on behalf of david.pratt@outlook.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>
Sent: Monday, January 16, 2017 6:08 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Multi-Value Fields
Sent: Monday, January 16, 2017 6:08 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Multi-Value Fields
I am looking at the MS Access Template called ISSUES. It utilizes a field property of "allow multi-values". Are there any potential issues with using this property?
For a small number of items, it seems to be a simple option as compared to creating a many to many relationship between two tables with a join table. But sometimes I see guidance from experienced developers to not use some of the Access options due to problems which might show up later.
Thanks, David
__._,_.___
Posted by: Duane Hookom <duanehookom@hotmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
.
__,_._,___
Tidak ada komentar:
Posting Komentar