Concur wholeheartedly. All the extra coding to extract out the data too…
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, January 17, 2017 4:28 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Multi-Value Fields
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
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
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Posted by: Liz Ravenwood <Liz_Ravenwood@beaerospace.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar