Record Dependency

External Since: Jun 12, 2007 Posts: 19

Oops, Ken, I forgot one thing...
I may not be using the correct terms for my fields, so I wanted to clarify
how I'm using the Report Type, Category. The Report Type is to show if the
report was an Ad Hoc Query, Batch, Interface, etc. The Category is to show
the type of Ad Hoc Query, such as Headcount, Turnover, etc.
Thanks, again.
Raven

--
Thanks, for spreading the knowledge.
Raven

"Ken Sheridan" wrote:

> Essentially the Reports table models the many to many relationships between
> the others in the way Steve describes, by having foreign key columns which
> reference the primary keys of each of the referenced tables.
>
> One point you need to look a little more closely at is that of the
> relationships involving report categories and report types. It may be that
> by referencing both the Categories and ReportTypes tables in the Reports
> table you are introducing redundancy. If all reports of a particular Type
> fall into the same Category, then you only need reference the ReportTypes
> table in the Reports table, i.e. you only need a ReportTypeID column not a
> CategoryID column. The ReportTypes table would then have a categoryID
> foreign key column referncing the primary key of Categories, so the
> relationships are like so:
>
> Reports>-----ReportTypes>----Categories
>
> It could be the other way round of course, with category implying type
> rather than type implying category. However, if its as above, in the more
> formal terminology of the relational model, to have both ReportTypeID and
> CategoryID columns in Reports mean that the CategoryID column is transitively
> functionally dependent on the key of Reports, ReportID determines TypeID
> determines CategoryID. This would mean the table is not in Third Normal Form
> (3NF), which requires all non-key columns to be functionally dependant on the
> whole of the key of the table. Where a transitive functional dependency is
> present the door is open to inconsistent data; in your case there would be
> nothing to stop a row being entered in Reports with the same ReportTypeID and
> different CategoryID values.
>
> If neither type implies category, nor category implies type then there is no
> transitive functional dependency of course, so having both columns in the
> Reports table is legitimate.
>
> You may have noticed that I differ from Steve (and many others!) in the
> naming conventions I use. I favour the approach recommended by Joe Celko
> that table names should as far as possible be plural or collective nouns
> (reflecting the fact that tables are sets), and that column names should as
> far as possible be singular nouns (reflecting the fact that each column
> represents an attribute). In both cases the names should be as close as
> possible to real English words describing the entity type or attribute type
> in question, avoiding tags like 'tbl' as these merely get in the way of the
> semantics. I'm by no means proscriptive about this though; each to his own.
>
> Ken Sheridan
> Stafford, England
>
> "Raven" wrote:
>
> > Sorry, I thought the additional information went through.
> > I would like to keep a track of all the report requests that's processed
> > through our reporting dept.
> > I have created an inventory table that will be used to store the data that I
> > input on the inventory form.
> > On the table I have the following fields:
> > Report ID; Report Type; Category/Description; Customer/ID/Location;
> > Frequency/Date; and Processor
> > I have created child tables based on these fields with autonumbered ids.
> > This is where I get confused... I'm not sure how to create the relationship
> > of these tables based on the ids from each table. Hope that makes sense.
> >
> > Thanks, for spreading the knowledge.
> > Raven
> >
> >
> > "John W. Vinson/MVP" wrote:
> >
> > > On Thu, 24 Jul 2008 15:46:10 -0700, Raven
> > > <Raven.DeleteThis@discussions.microsoft.com> wrote:
> > >
> > > >I am creating a db for our reporting area. The db will store information,
> > > >such as the type of reports, frequency, processed by, etc. I am having
> > > >trouble however, setting the relationship of the tables. In addition, when I
> > > >create the form to enter the data, the table I created does not update,
> > > >properly with the info. Can anyone help with this issue?
> > >
> > > Not without knowing more about the problem, no. You can see your
> > > database; we cannot. What are the tables? HOw are they related? What
> > > is the Recordsource of the form?
> > >
> > > --
> > >
> > > John W. Vinson/MVP
> > >
>

External Since: Jun 23, 2008 Posts: 193

"Steve" <nonsense RemoveThis @nomsense.com> wrote in message
news:eImdndFZE52QehTVnZ2dnUVZ_uWdnZ2d@earthlink.com...
>
> ......... Don't know what frequency is ...........
>
> Steve

Showing off the quality of your work? I thought at one time you pretended to
be an engineer? Any first year student would understand frequency and would
know that the OP was talking about how often a report is produced.

These newsgroups are provided by Microsoft for FREE peer to peer support.
Your type of help is not needed.

John... Visio MVP