<font size=2 face="sans-serif">Cool! And we still have today to register!
</font>
<br><font size=2 face="sans-serif">Unfortunately, I'm thinking IBM will
not pay for me to go, but everyone else have fun. :-)</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Karen Barrett <kayandjade@aol.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">powerh-l@lists.sowder.com</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">03/06/2015 09:40 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">PH conventions</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">powerh-l-bounces+mohmes=us.ibm.com@lists.sowder.com</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Arial">There is in fact a convention being held
in CA soon by the new owner of PH, Unicom Global. </font><a href=http://unicomsi.com/files/3014/2427/4609/UNICOM_Global_CAB_and_UGMs_at_PickFair.2015.03.27.pdf><font size=2 face="Arial">http://unicomsi.com/files/3014/2427/4609/UNICOM_Global_CAB_and_UGMs_at_PickFair.2015.03.27.pdf</font></a><font size=2 face="Arial">
<br>
</font>
<br><font size=2 face="Arial">Karen Barrett<br>
</font>
<br><font size=2 face="Arial"><br>
</font>
<br><font size=2 face="Arial">-----Original Message-----<br>
From: powerh-l-request <powerh-l-request@lists.sowder.com></font>
<br><font size=1 face="Tahoma"><br>
Today's Topics:<br>
<br>
1. RE:Hierarchical vs. Parallel linkage<br>
(Matt<br>
Ohmes)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message:<br>
1<br>
Date: Fri, 6 Mar 2015 08:52:06 -0600<br>
From: Matt Ohmes<br>
<</font><a href=mailto:mohmes@us.ibm.com><font size=1 color=blue face="Tahoma"><u>mohmes@us.ibm.com</u></font></a><font size=1 face="Tahoma">><br>
Subject: RE: Hierarchical vs. Parallel linkage<br>
To:<br>
"Richard Witkopp" <</font><a href=mailto:RWitkopp@phxa.com><font size=1 color=blue face="Tahoma"><u>RWitkopp@phxa.com</u></font></a><font size=1 face="Tahoma">><br>
Cc: PowerHouse listserver<br>
<</font><a href="mailto:powerh-l@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l@lists.sowder.com</u></font></a><font size=1 face="Tahoma">><br>
Message-ID:<br>
<</font><a href="mailto:OF23FDD4C1.837CAD0A-ON86257E00.00503F68-86257E00.0051AE2C@us.ibm.com"><font size=1 color=blue face="Tahoma"><u>OF23FDD4C1.837CAD0A-ON86257E00.00503F68-86257E00.0051AE2C@us.ibm.com</u></font></a><font size=1 face="Tahoma">><br>
Content-Type:<br>
text/plain; charset="utf-8"<br>
<br>
Hey Richard!<br>
You are probably one of the last<br>
people who remember my old MattO (Oh, not <br>
zero) tag. :-)<br>
<br>
I don't know if<br>
there are still PH conventions, but I doubt it. Oddly <br>
enough I gave a more<br>
complete version of this many, many years ago at a <br>
Cognos convention and it<br>
was my biggest ego boost moment. The room not <br>
only filled completely, but<br>
there were people sitting on the floor at my <br>
feet so they could see it! <br>
<br>
I<br>
wish I still had that original paper, as it seems to be a pretty <br>
confusing<br>
topic still. (Anyone have one in their archives?)<br>
<br>
Also, If you have a QTP<br>
with all those files, you might also be interested <br>
in another paper I wrote<br>
(years ago) called the "Care and Feeding of QTP". <br>
I have a PDF of it still I<br>
can send you if you'd like (I can't post it to <br>
the list, if I recall). <br>
However, that has more to do with output timing <br>
than hierarchical vs. parallel<br>
linkage.<br>
<br>
My main advice for debugging Access statements has always been, take<br>
the <br>
Access and put it in Quiz and write a VERY basic Report statement that<br>
<br>
dumps something from every files. Then go look at the files
individually<br>
<br>
and make sure they match what you see. If that works, they your problem
<br>
is<br>
elsewhere. And honestly, with QTP, it is usually the "elsewhere"
that <br>
is the<br>
problem. :-)<br>
<br>
This has been fun!<br>
Cheers,<br>
Matt<br>
<br>
<br>
<br>
From: "Richard<br>
Witkopp" <</font><a href=mailto:RWitkopp@phxa.com><font size=1 color=blue face="Tahoma"><u>RWitkopp@phxa.com</u></font></a><font size=1 face="Tahoma">><br>
To: "PowerHouse listserver"<br>
<</font><a href="mailto:powerh-l@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l@lists.sowder.com</u></font></a><font size=1 face="Tahoma">><br>
Date: 03/05/2015 06:29 PM<br>
Subject: RE:<br>
Hierarchical vs. Parallel linkage<br>
Sent by: <br>
powerh-l-bounces+mohmes=</font><a href=mailto:us.ibm.com@lists.sowder.com><font size=1 color=blue face="Tahoma"><u>us.ibm.com@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
<br>
<br>
<br>
Nice, not-a-zero!<br>
<br>
<br>
Are there still Powerhoose conventions? This would make a good<br>
<br>
presentation.<br>
<br>
I need to re-read this thing about 4 times. I?ve got a qtp<br>
with about 5 <br>
parallel legs and 3 hierarchical files down each leg and it<br>
doesn?t do <br>
what it looks like it should do.<br>
<br>
From:<br>
powerh-l-bounces+rwitkopp=</font><a href=mailto:phxa.com@lists.sowder.com><font size=1 color=blue face="Tahoma"><u>phxa.com@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
[<br>
</font><a href="mailto:powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com?"><font size=1 color=blue face="Tahoma"><u>mailto:powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com</u></font></a><font size=1 face="Tahoma">]
On Behalf Of<br>
<br>
Matt Ohmes<br>
Sent: Thursday, March 05, 2015 3:57 PM<br>
To: PowerHouse<br>
listserver<br>
Subject: Hierarchical vs. Parallel linkage<br>
<br>
Hi all, <br>
I promised<br>
I would write up something on the differences between <br>
Hierarchical and<br>
Parallel linkage in Quiz (and QTP), so here we go. (And <br>
for those of you who<br>
know all this already, please forgive my trip down <br>
memory lane.) <br>
<br>
Oh, and<br>
I'm assuming no bugs in the product regarding syntax. :-) <br>
<br>
Differences<br>
between Hierarchical and Parallel linkage in Quiz (and QTP) <br>
<br>
In all examples<br>
below, we will use 3 files. Assume all are indexed files, <br>
keyed on Emp_No<br>
<br>
File Employees: 5 records; <br>
Emp_No Emp_Name <br>
1 Bob <br>
2 Mary <br>
3<br>
Pat <br>
4 Kim <br>
5 Sean <br>
<br>
File Paychecks: 5 records <br>
Emp_No <br>
Pay_Date Amt <br>
1 2015-01-01 100 (Bob) <br>
1 2015-01-15 200 <br>
(Bob) <br>
2 2015-01-01 300 (Mary) <br>
2 2015-01-15 400 (Mary)<br>
<br>
3 2015-01-15 600 (Pat) <br>
Note: 4 Kim and 5 Sean just started and<br>
have not been paid yet) <br>
<br>
File Dependents: 4 records; <br>
Emp_No Dep_Name <br>
1 <br>
Bob Jr (Bob's 1st dependent)
<br>
1 Bobbie
(Bob's<br>
2nd dependent) <br>
2 Marie
(Mary's dependent) <br>
5 Shawn <br>
(Sean's dependent) <br>
Note: 3 Pat and 4 Kim do not have any dependents <br>
<br>
This<br>
will be my Report statement for ALL examples: <br>
Report & <br>
Emp_No of<br>
Employees & <br>
Emp_Name of Employees & <br>
Pay_Date of Paychecks & <br>
<br>
Amt of Paychecks & <br>
Dep_Name of Dependents <br>
<br>
First Hierarchical linkage:<br>
<br>
Access Employees & <br>
Link Emp_No of Employees to Emp_No of Paychecks & <br>
<br>
Link Emp_No of Employees to Emp_No of Dependents <br>
<br>
Emp_No Emp_Name <br>
Pay_Date Amt Dep_Name <br>
1 Bob 2015-01-01 100
Bob Jr<br>
<br>
1 Bob 2015-01-01 100
Bobbie <br>
1 Bob <br>
2015-01-15 200 Bob Jr <br>
1 Bob 2015-01-15 200
Bobbie <br>
2 <br>
Mary 2015-01-01 300 Marie
<br>
2 Mary 2015-01-15 400
<br>
Marie <br>
<br>
Obvious problems. Pat, Kim, and Sean are not showing up at all because<br>
no <br>
files are optional. I'm assuming the use of Optional in hierarchical<br>
<br>
linkage is well understood so I won't go into that discussion here. This<br>
<br>
post is about parallel linkage. :-) <br>
<br>
A bigger problem with the report is<br>
that paycheck and dependent records <br>
are being duplicated. Hierarchical linkage<br>
is simply wrong for this data; <br>
the results make no sense. <br>
<br>
Using<br>
hierarchical linkage for this data is essentially saying, for each <br>
paycheck an<br>
employee has received, read down the list of all their <br>
dependents. That makes<br>
no sense. Just as it would make no sense to say, <br>
for each dependent an<br>
employee has, show me every time they have been <br>
paid. The number of paychecks<br>
I receive is based on how long I have <br>
worked for my employeer, not how many<br>
dependents I have. Similarly, the <br>
number of dependents I have is not based on<br>
how long I have worked for my <br>
employer. <br>
<br>
Paychecks and Dependents are<br>
both, obviously related to Employees, but <br>
they are NOT RELATED TO ONE ANOTHER.<br>
<br>
<br>
Instead of one of these files "driving" the other, they should
be read in<br>
<br>
parallel; i.e. at the same time. THIS is why we have parallel linkage.<br>
<br>
Parallel linkage is saying, for each employee, show me each of their<br>
<br>
paychecks AND each of their dependents. <br>
<br>
Let's try parallel linkage in the<br>
Access statement and what that does to <br>
our report results. <br>
<br>
Access<br>
Employees & <br>
Link Emp_No of Employees to Emp_No of Paychecks & <br>
AND<br>
Emp_No of Employees to Emp_No of Dependents <br>
<br>
Emp_No Emp_Name Pay_Date <br>
Amt Dep_Name <br>
1 Bob 2015-01-01 100
Bob Jr <br>
1 Bob <br>
2015-01-15 200 Bobbie <br>
2 Mary 2015-01-01 300
Marie <br>
2 <br>
Mary 2015-01-15 400 <br>
3 Pat 2015-01-15 600
<br>
5 Sean<br>
Shawn <br>
<br>
This makes more sense for this data. Each paycheck is reported once<br>
and <br>
each dependent is reported once. <br>
Notice, as long as there is at least<br>
one record FROM ANY of the parallel <br>
files you get a record complex returned.<br>
Parallel files are, more or less, <br>
"semi-optional". <br>
<br>
However, also notice<br>
employee 4 Kim was not reported. This was because <br>
Kim did not have any<br>
paychecks (yet) or dependents. If you want to see Kim <br>
on the report as well,<br>
make ANY of the parallel files optional; it doesn't <br>
make any difference which<br>
one because of the "semi-optional" nature of <br>
parallel files. <br>
<br>
Access<br>
Employees & <br>
Link Emp_No of Employees to Emp_No of Paychecks & <br>
AND<br>
Emp_No of Employees to Emp_No of Dependents Optional <br>
<br>
Emp_No Emp_Name <br>
Pay_Date Amt Dep_Name <br>
1 Bob 2015-01-01 100
Bob Jr<br>
<br>
1 Bob 2015-01-15 200
Bobbie <br>
2 Mary <br>
2015-01-01 300 Marie <br>
2 Mary 2015-01-15 400
<br>
3 Pat <br>
2015-01-15 600 <br>
4 Kim <br>
5 Sean
Shawn<br>
<br>
<br>
To be honest, parallel linkage is not that common. It is fair to ask, "If<br>
<br>
two files aren't related to one another, why are you writing a report with<br>
<br>
both of them on it?" But it does have its uses from time to
time. <br>
<br>
I<br>
hope that explanation helps. (It was fun writing about good old Quiz <br>
again<br>
after all these years.) <br>
Cheers, <br>
Matt<br>
securemail.phxa.com made the following<br>
annotations<br>
---------------------------------------------------------------------<br>
<br>
NOTICE:<br>
The information contained in this e-mail and <br>
any attachments is confidential<br>
and may be privileged <br>
or otherwise protected from disclosure.This e-mail is<br>
<br>
intended solely for the use of the named addressee. <br>
Any other use, printing,<br>
copying, disclosure or <br>
dissemination may be subject to legal restriction. If<br>
<br>
you are not the intended recipient, please contact the <br>
sender and delete all<br>
copies including any<br>
attachments.<br>
<br>
-----------------------------------------------------------------------<br>
=<br>
= = = = = = = = = = = = = = = = = = = = = = = = = = =<br>
Mailing list:<br>
</font><a href="mailto:powerh-l@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
Subscribe: 'subscribe' in message body to<br>
<br>
</font><a href="mailto:powerh-l-request@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l-request@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
Unsubscribe: 'unsubscribe &lt;password&gt;'<br>
in message body to<br>
<br>
</font><a href="mailto:powerh-l-request@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l-request@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
</font><a href="http://lists.sowder.com/mailman/listinfo/powerh-l" target=_blank><font size=1 color=blue face="Tahoma"><u>http://lists.sowder.com/mailman/listinfo/powerh-l</u></font></a><font size=1 face="Tahoma"><br>
This<br>
list is closed, thus to post to the list you must be a subscriber.<br>
Add<br>
'site:lists.sowder.com powerh-l' to your search terms to search the <br>
list<br>
archive at Google.<br>
<br>
-------------- next part --------------<br>
An HTML<br>
attachment was scrubbed...<br>
URL:<br>
<</font><a href="http://lists.sowder.com/pipermail/powerh-l/attachments/20150306/8c610fe4/attachment.htm" target=_blank><font size=1 color=blue face="Tahoma"><u>http://lists.sowder.com/pipermail/powerh-l/attachments/20150306/8c610fe4/attachment.htm</u></font></a><font size=1 face="Tahoma">><br>
<br>
------------------------------<br>
<br>
--<br>
=<br>
= = = = = = = = = = = = = = = = = = = = = = = = = = =<br>
Mailing list:<br>
</font><a href="mailto:powerh-l@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
Subscribe: &quot;subscribe&quot; in message body to<br>
</font><a href="mailto:powerh-l-request@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l-request@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
Unsubscribe: &quot;unsubscribe<br>
&lt;password&gt;&quot; in message body to<br>
</font><a href="mailto:powerh-l-request@lists.sowder.com"><font size=1 color=blue face="Tahoma"><u>powerh-l-request@lists.sowder.com</u></font></a><font size=1 face="Tahoma"><br>
</font><a href="http://lists.sowder.com/mailman/listinfo/powerh-l" target=_blank><font size=1 color=blue face="Tahoma"><u>http://lists.sowder.com/mailman/listinfo/powerh-l</u></font></a><font size=1 face="Tahoma"><br>
This<br>
list is closed, thus to post to the list you must be a subscriber.<br>
Add<br>
'site:lists.sowder.com powerh-l' to your search terms to search the list
archive<br>
at Google.<br>
<br>
End of powerh-l Digest, Vol 113, Issue<br>
15<br>
*****************************************<br>
</font><tt><font size=2>--<br>
= = = = = = = = = = = = = = = = = = = = = = = = = = = =<br>
Mailing list: powerh-l@lists.sowder.com<br>
Subscribe: 'subscribe' in message body to powerh-l-request@lists.sowder.com<br>
Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to
powerh-l-request@lists.sowder.com<br>
</font></tt><a href="http://lists.sowder.com/mailman/listinfo/powerh-l"><tt><font size=2>http://lists.sowder.com/mailman/listinfo/powerh-l</font></tt></a><tt><font size=2><br>
This list is closed, thus to post to the list you must be a subscriber.<br>
Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list archive at Google.</font></tt>
<br>