On Mon, 09 Apr 2012 10:19:55 GMT, Liam Murphy <(E-Mail Removed)> wrote:
>Also, with this setup, how would I enable the ability to assign multiple issues to a particular date and boat? My
> first design of this DB had a similar setup for the issues, but I found on the input form, I had to keep
> adding input blocks as I found surveys with multiple errors on a page, which is why I went to a yes/no field
> for each error type, so I could more easily assign multiple errors to a single survey. I have a minimum of
> 1 per date (no errors), and an unlimited maximum.
>
ok... found your previous discussion.
You're missing the point. With the normalized structure you don't HAVE any
checkboxes, and you don't NEED the Abs() function. You just count records!
The PageIssues table I'm suggesting would have multiple records for each page.
It's MUCH BETTER than the wide-flat checkbox interface in this regard; you can
add any needed number of records to the table, each with its own PageID (a
Long Integer number foreign key link to the Pages table), its own IssueID (a
Long Integer number foreign key link to the Issues table), a date/time, and
perhaps optional other fields for details of this issue for this page.
You can create a unique multifield index if you wish to *prevent* entering the
same error twice for the same page on the same date, if you wish; but the
default is that there are no limits.
I would NOT use Lookup Fields, period; they don't give you *anything* that you
can't get just as simply by using a form. All the Lookup Field does is conceal
the actual contents of your table behind a combo box.
--
John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/For...-US/accessdev/
http://social.answers.microsoft.com/.../en-US/addbuz/
and see also
http://www.utteraccess.com
Similar Threads
