<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2>Although I can't comment on the enhancement request at this
time, other than to say it's on my list and I fully understand why it's
needed/wanted, I couldn't help but jump in to comment on Ken's
observation.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2>As it happens, the person who is considered the creator of
QTP did write QDESIGN.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2>This is one of those anomalies that we can't
change for historical reasons. By default, GET verbs are required. There is
some logic around PRIMARY and DETAIL gets to handle situations in the FIND and
DETAIL FIND procedures. However, if you do a GET on a SECONDARY without saying
OPTIONAL, it's required. QDESIGN generates (and has always generated as far as I
know) the GET OPTIONAL for SECONDARY files in the FIND and DETAIL FIND
regardless of whether you have OPTIONAL on the ACCESS statement.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2>So the requested REQUIRED option would only apply to the
OPTIONAL generated in the FIND and DETAIL FIND because it's not needed
elsewhere.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=156074614-14112007><FONT face=Arial
color=#0000ff size=2>Bob</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
powerh-l-bounces+bob.deskin=cognos.com@lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com@lists.sowder.com] <B>On Behalf
Of </B>Ken Langendock<BR><B>Sent:</B> November 14, 2007 9:25 am<BR><B>To:</B>
fernando.olmos@hpa.com.au; powerh-l@lists.sowder.com<BR><B>Subject:</B> RE:
Stupid question about Primary and Secondary<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2>True, but I understand the original design, I'd just
like to have the option of creating a link that is REQUIRED before a record is
retrieved just like </FONT></SPAN><SPAN
class=515461414-14112007><FONT face=Arial color=#0000ff size=2>in
QTP.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2>Access Employees &</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2> link to Security</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2>The same in Qdesign would be:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2>File Employees Primary</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2>File Security Secondary REQUIRED</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2>Or you are correct it might have been better to code
Qdesign originally like this:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2>File Employees Primary</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Courier
color=#0000ff size=2>File Security Secondary (REQUIRED automatically unless
the programmer adds OPTIONAL)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2>I think that if the same programmer who created QTP wrote
Qdesign, it might have happened this way. But I know that would be a change
that will NOT happen at this point so the REQUIRED option would be a nice to
have enhancement.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2>Ken</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515461414-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com] <B>On
Behalf Of </B>fernando.olmos@hpa.com.au<BR><B>Sent:</B> November 13, 2007
11:35 PM<BR><B>To:</B> Ken@Langendock.com;
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: Stupid question about Primary
and Secondary<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=544073304-14112007><FONT face=Arial color=#0000ff
size=2>Thanks Ken.</FONT></SPAN></DIV>
<DIV><SPAN class=544073304-14112007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=544073304-14112007><FONT face=Arial color=#0000ff size=2>I
guess the logic behind this is to "encourage" the developer to note that all
links to the primary table are optional by default and should be, in the case
where the underlying tables do not yield any data. Therefore, "some" data will
be available to the user if the screen was hashed out quickly - so to speak,
to give something to the user. Of course when screens are developed, they
seldom stay the way PH intended them to stay!</FONT></SPAN></DIV>
<DIV><SPAN class=544073304-14112007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=544073304-14112007><FONT face=Arial color=#0000ff
size=2>cheers</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial color=#0000ff size=2>Kind
regards,</FONT></SPAN> </P>
<P><SPAN lang=en-us><FONT face="Courier New" size=2>---</FONT></SPAN>
<BR><SPAN lang=en-au><B><FONT face=Arial size=2>Fernando
Olmos</FONT></B></SPAN> <BR><SPAN lang=en-au><FONT face=Arial color=#808080
size=2>Senior Analyst Programmer</FONT></SPAN> <BR><SPAN lang=en-au><B><FONT
face=Arial color=#000080 size=2>HPA</FONT> <FONT face=Arial color=#0000ff
size=2>– A Salmat Company</FONT></B><BR><FONT face=Arial color=#808080
size=2>Direct: 02 9311 5411<BR>Fax: 02 9311 5166<BR>Mobile: 0434 879
784</FONT></SPAN> <BR><SPAN lang=en-au></SPAN><A
href="outbind://72-000000004873297C6F02D34791376BCD02053396070089F66260EA86FC45B9843CB9AE160C240000003C72B40000B1FC7253EE1378408169587124093AAC000000660A050000/www.hpa.com.au"><SPAN
lang=en-au><U></U><U><B></B></U><U><B></B></U><U><B><FONT face=Arial
color=#0000ff size=2>www.hpa.com.au</FONT></B></U></SPAN></A><SPAN
lang=en-au></SPAN> </P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
Ken@Langendock.com [mailto:Ken@Langendock.com] <BR><B>Sent:</B> Wednesday,
14 November 2007 3:28 PM<BR><B>To:</B> Fernando Olmos;
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: Stupid question about
Primary and Secondary<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=424044703-14112007><FONT face=Arial
color=#0000ff size=2>There is no way currently to do what you want. I
requested an enhancement with Cognos to add a "REQUIRED" option to a
secondary file to do this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=424044703-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=424044703-14112007><FONT face=Arial
color=#0000ff size=2>Until then Hard code the find and comment out the
OPTIONAL on the secondary GET</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=424044703-14112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=424044703-14112007><FONT face=Arial
color=#0000ff size=2>Ken</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com] <B>On
Behalf Of </B>fernando.olmos@hpa.com.au<BR><B>Sent:</B> November 13, 2007
7:28 PM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> Stupid
question about Primary and Secondary<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>I thought that the following code would make the
ORDER_MASTER table *not* optional!</FONT> </P>
<P><FONT face=Arial size=2>> screen ert</FONT> <BR><FONT face=Arial
size=2>> file customers in isdb</FONT> <BR><FONT face=Arial size=2>>
file order_master in isdb secondary</FONT> <BR><FONT face=Arial size=2>>
build list detail</FONT> </P>
<P><FONT face=Arial size=2>> PROCEDURE PATH</FONT> <BR><FONT face=Arial
size=2>> BEGIN</FONT> <BR><FONT face=Arial
size=2>> LET PATH = 1</FONT> <BR><FONT face=Arial
size=2>> END</FONT> <BR><FONT face=Arial
size=2>> PROCEDURE FIND</FONT> <BR><FONT face=Arial
size=2>> BEGIN</FONT> <BR><FONT face=Arial
size=2>> GET CUSTOMERS SEQUENTIAL</FONT>
<BR><FONT face=Arial size=2>> GET ORDER_MASTER
OPTIONAL</FONT> <BR><FONT face=Arial size=2>>
END</FONT> </P>
<P><FONT face=Arial size=2>Yet it does. Why?</FONT> </P>
<P><FONT face=Arial size=2>How can I declare the FILE statement to not place
an OPTIONAL on GET ORDER_MASTER?</FONT> </P>
<P><FONT face=Arial size=2>Thanks</FONT> </P>
<P><FONT face=Arial color=#0000ff size=2>Kind regards,</FONT> </P>
<P><FONT face="Courier New" size=2>---</FONT> <BR><SPAN lang=en-au><B><FONT
face=Arial size=2>Fernando Olmos</FONT></B></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial color=#808080 size=2>Senior Analyst
Programmer</FONT></SPAN> <BR><SPAN lang=en-au><B><FONT face=Arial
color=#000080 size=2>HPA</FONT> <FONT face=Arial color=#0000ff size=2>– A
Salmat Company</FONT></B><BR><FONT face=Arial color=#808080 size=2>Direct:
02 9311 5411<BR>Fax: 02 9311 5166<BR>Mobile: 0434 879 784</FONT></SPAN>
<BR><SPAN lang=en-au></SPAN><A
href="outbind://72-000000004873297C6F02D34791376BCD02053396070089F66260EA86FC45B9843CB9AE160C240000003C72B40000B1FC7253EE1378408169587124093AAC000000660A050000/www.hpa.com.au"><SPAN
lang=en-au><U></U><U><B></B></U><U><B></B></U><U><B><FONT face=Arial
color=#0000ff size=2>www.hpa.com.au</FONT></B></U></SPAN></A><SPAN
lang=en-au></SPAN> </P><BR><PRE>**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you received this e-mail in error, please notify the HPA Postmaster, postmaster@hpa.com.au,
then delete the e-mail.
This footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services. For more
information about use, disclosure and access see our Privacy Policy at
www.hpa.com.au
**********************************************************************
</PRE></BLOCKQUOTE><PRE>**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you received this e-mail in error, please notify the HPA Postmaster, postmaster@hpa.com.au,
then delete the e-mail.
This footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services. For more
information about use, disclosure and access see our Privacy Policy at
www.hpa.com.au
**********************************************************************
</PRE></BLOCKQUOTE></BODY></HTML>