Showing posts with label ability. Show all posts
Showing posts with label ability. Show all posts

Monday, March 19, 2012

Details grouping

Hi,
what is the details grouping for? Like, we have the ability to set up
groups, why do we also need details grouping?
thanks
MattMatt,
You may not want to show the lowest level of detail returned by your
query, say you returned order lines in your query, but you only want to
show order totals. Instead of having an order group and a detail
section that needs to be hidden, you could just have detail section
grouped on order.
You may say that's actually quite inefficient as you should change the
query to just return order totals, and you'd be right, but consider if
that grouping was parameter driven. You might want to group on sales
rep, customer or product. This is when this scenario makes sense.
Hope that helps.
Cheers
Chris
Matt wrote:
> Hi,
> what is the details grouping for? Like, we have the ability to set up
> groups, why do we also need details grouping?
> thanks
> Matt|||Ah I see. Thanks Chris - for taking the time to write a nice clear
explanation
"Chris McGuigan" <chris.mcguigan@.zycko.com> wrote in message
news:e6XfTURiFHA.1204@.TK2MSFTNGP12.phx.gbl...
> Matt,
> You may not want to show the lowest level of detail returned by your
> query, say you returned order lines in your query, but you only want to
> show order totals. Instead of having an order group and a detail
> section that needs to be hidden, you could just have detail section
> grouped on order.
> You may say that's actually quite inefficient as you should change the
> query to just return order totals, and you'd be right, but consider if
> that grouping was parameter driven. You might want to group on sales
> rep, customer or product. This is when this scenario makes sense.
> Hope that helps.
> Cheers
> Chris
>
> Matt wrote:
> > Hi,
> >
> > what is the details grouping for? Like, we have the ability to set up
> > groups, why do we also need details grouping?
> >
> > thanks
> >
> > Matt
>

Tuesday, February 14, 2012

Design advise

I have been given a DB that currently stores Organizations. I need to add the ability to track multiple contacts for the Organizations. The DB has several one-to-many relationships on the Organizations table, such as Documents and Notes. I would like to track these by contact as well as the organization.

Is it possible to add a tblcontact and a one-to-many relationships to the Organizations table as well as to the tblDocuments and tblNotes?

I appreciate any suggestions.

tblOrg (OrgID)

tblDocuments (DocID, OrgID)

tblNotes (NoteID, OrgID)

tblContact ?

I also wanted to mention that we would be tracking organiztions and individuals.

I appreciate any suggestions on how to add to the existing Database.

|||

Hi Jack,

sure we can add a relation between the tblContact and tblOrg.

If your Documents and Notes belongs to a contact not Org, you need to create on-to-many relationship from tblContact to tblDocuments. When you need to track documents of an Org, you can first get the contacts and then get their docs.

|||I think I'm going to stick with the one org table and put everyone in that table. I will add a way to determine if the record is an organization or an individual (record type). I can create a relation table that contains the followng four fields (orgid, relationshipid, relatedorgid, reciprocalid).