This is for Todd and Jim
Is there a way to change the master table using RB? I just finished
recreating a report that had the wrong master table for my needs. I
couldn't see any other way of changing the master so I started from scratch.
Todd I like the idea of always using the company table as master.
Mark Dupuis
-----Original Message-----
From: Jim Stetter [mailto:jimstetter@...]
Sent: Thursday, February 28, 2002 1:29 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Linking Tables
Todd,
We have multiple companies in our database, so I always use Company as the
master table. (usually have to inculde Company Name or something from
Company table anyway). I really hadn't given any thought to your second
point, but I can see the added benefit you describe. In the early days of
using RB, it was common to find I needed to change the master table and
indeed it is a royal pain to change. Yes, I also see an increase in
performance using this methodology.
Here's a few other tips I have found useful in RB filters:
Specify filter data using the same hierarchy as your joins ei
Company.Company = "SN2", LaborHed.PayrollDate in-range 2/1/2002, 2/15/2002,
NOT LaborHed.PayrollDate in-range....., Company.Company = "SN2"
Use in-range instead of in-list where possible
Use Begins "XXXX" instead of >="XXXX" and <="XXXXendingvalue". Very
useful for grabbing all PartNum that start with "XXXX" only. From my
experience, most Vantage users have assigned some logical meaning to their
part number system.
Good Luck,
Jim Stetter
-----Original Message-----
From: Todd Caughey [mailto:caugheyt@...]
Sent: Thursday, February 28, 2002 12:34 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Linking Tables
Jim,
Is starting with company only for performance reasons or does it make the
"real" master table (below company) easier to change if you need to ?
Half
a dozen times I've gotten a report almost done (all the formatting and
agg
& calc fields) only to find I should have had a different master table. A
real pain to change in RB. This sounds like a way to avoid the pain.
-Todd C.
-----Original Message-----
From: Jim Stetter [mailto:jimstetter@...]
Sent: Thursday, February 28, 2002 10:56 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Linking Tables
Wendy,
Here are a few pointers that usually work well for me:
1. I always start with Company as the master table. Also, include
Company.Company in the filter/select even if you only have one company in
your database.
2. When you use detail tables (OrderDtl, LaborDtl..), use the coresponding
header table (OrderHed, LaborHed..) and join the detail table to the
Header
table. There are some situation where this doesn't apply. One that come to
mind would be the join between the PackDtl and OrderRel. (But you might
have
joined PackDtl to PackHed!)
3. Avoid linking 2 or more tables at the same level (Empbasic and Indirect
both to LaborDtl ). This causes the query to attempt to lookup both
dependent records and can slow you down.
4. Structure your links such that the tables with fewer records are to the
left (joins go left to right).
To demonstrate this technique, here is how I would create the joins for
your
example:
Company ------->Empbasic------->LaborHed-------->LaborDtl--------->Indirect
(Left Outer)
by Company by Company by Company by
Company
and EmpID and EmployeeNum and
IndirectCode
and LaborHedSeq
HTH
Jim Stetter
-----Original Message-----
From: Wendy Bowen (Pursche) [mailto:wpursche@...]
Sent: Thursday, February 28, 2002 9:08 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Linking Tables
Okay, all you Crystal and RB gurus............what is the best way to link
these 3 tables together?
Labordtl
Indirect
Empbasic
I have them linked together for a Crystal report and the report seems to
take longer to compile than it should. Granted, I have quite a few fields
displayed on the report, but otherwise I don't think it should take a
while
to compile. Right now I have the tables linked by:
Labordtl - Indirect: company, indirect code (left outer join) I need all
data, not just indirect
Labordtl - Empbasic: company, employee num/id (equal join)
Thanks!
Wendy Bowen
Network Administrator
Schmald Tool & Die, Inc.
(810) 743-1600 ext.323
wpursche@...
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Is there a way to change the master table using RB? I just finished
recreating a report that had the wrong master table for my needs. I
couldn't see any other way of changing the master so I started from scratch.
Todd I like the idea of always using the company table as master.
Mark Dupuis
-----Original Message-----
From: Jim Stetter [mailto:jimstetter@...]
Sent: Thursday, February 28, 2002 1:29 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Linking Tables
Todd,
We have multiple companies in our database, so I always use Company as the
master table. (usually have to inculde Company Name or something from
Company table anyway). I really hadn't given any thought to your second
point, but I can see the added benefit you describe. In the early days of
using RB, it was common to find I needed to change the master table and
indeed it is a royal pain to change. Yes, I also see an increase in
performance using this methodology.
Here's a few other tips I have found useful in RB filters:
Specify filter data using the same hierarchy as your joins ei
Company.Company = "SN2", LaborHed.PayrollDate in-range 2/1/2002, 2/15/2002,
NOT LaborHed.PayrollDate in-range....., Company.Company = "SN2"
Use in-range instead of in-list where possible
Use Begins "XXXX" instead of >="XXXX" and <="XXXXendingvalue". Very
useful for grabbing all PartNum that start with "XXXX" only. From my
experience, most Vantage users have assigned some logical meaning to their
part number system.
Good Luck,
Jim Stetter
-----Original Message-----
From: Todd Caughey [mailto:caugheyt@...]
Sent: Thursday, February 28, 2002 12:34 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Linking Tables
Jim,
Is starting with company only for performance reasons or does it make the
"real" master table (below company) easier to change if you need to ?
Half
a dozen times I've gotten a report almost done (all the formatting and
agg
& calc fields) only to find I should have had a different master table. A
real pain to change in RB. This sounds like a way to avoid the pain.
-Todd C.
-----Original Message-----
From: Jim Stetter [mailto:jimstetter@...]
Sent: Thursday, February 28, 2002 10:56 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Linking Tables
Wendy,
Here are a few pointers that usually work well for me:
1. I always start with Company as the master table. Also, include
Company.Company in the filter/select even if you only have one company in
your database.
2. When you use detail tables (OrderDtl, LaborDtl..), use the coresponding
header table (OrderHed, LaborHed..) and join the detail table to the
Header
table. There are some situation where this doesn't apply. One that come to
mind would be the join between the PackDtl and OrderRel. (But you might
have
joined PackDtl to PackHed!)
3. Avoid linking 2 or more tables at the same level (Empbasic and Indirect
both to LaborDtl ). This causes the query to attempt to lookup both
dependent records and can slow you down.
4. Structure your links such that the tables with fewer records are to the
left (joins go left to right).
To demonstrate this technique, here is how I would create the joins for
your
example:
Company ------->Empbasic------->LaborHed-------->LaborDtl--------->Indirect
(Left Outer)
by Company by Company by Company by
Company
and EmpID and EmployeeNum and
IndirectCode
and LaborHedSeq
HTH
Jim Stetter
-----Original Message-----
From: Wendy Bowen (Pursche) [mailto:wpursche@...]
Sent: Thursday, February 28, 2002 9:08 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Linking Tables
Okay, all you Crystal and RB gurus............what is the best way to link
these 3 tables together?
Labordtl
Indirect
Empbasic
I have them linked together for a Crystal report and the report seems to
take longer to compile than it should. Granted, I have quite a few fields
displayed on the report, but otherwise I don't think it should take a
while
to compile. Right now I have the tables linked by:
Labordtl - Indirect: company, indirect code (left outer join) I need all
data, not just indirect
Labordtl - Empbasic: company, employee num/id (equal join)
Thanks!
Wendy Bowen
Network Administrator
Schmald Tool & Die, Inc.
(810) 743-1600 ext.323
wpursche@...
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/