<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=336200017-24072007><FONT face=Arial color=#0000ff size=2>I'll
add it to my list.</FONT></SPAN></DIV>
<DIV><SPAN class=336200017-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=336200017-24072007><FONT face=Arial color=#0000ff size=2>Please
keep in mind that the list is very large and we won't be doing everything. But I
do keep rolling it over from release to release.</FONT></SPAN></DIV>
<DIV><SPAN class=336200017-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=336200017-24072007><FONT face=Arial color=#0000ff
size=2>Bob</FONT></SPAN></DIV>
<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
[mailto:Ken@Langendock.com] <BR><B>Sent:</B> July 24, 2007 12:58
PM<BR><B>To:</B> Deskin, Bob; 'Daniel Rodríguez';
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: New feature suggestion :
Fields with entry if and proceduresdesignerID<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2>I would say all of the time.</FONT></SPAN><SPAN
class=118135416-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2>I'd say I create the number procedures in
about 25-30 percent of my screens (excluding selection, and launch
screens).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2>I'd say almost 100% of the cluster
screens</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2>Ken</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118135416-24072007><FONT face=Arial
color=#0000ff size=2></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> Deskin, Bob
[mailto:Bob.Deskin@Cognos.COM] <BR><B>Sent:</B> July 24, 2007 12:17
PM<BR><B>To:</B> Ken Langendock; Daniel Rodríguez;
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: New feature suggestion :
Fields with entry if and proceduresdesignerID<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=516051416-24072007><FONT face=Arial color=#0000ff size=2>How
often are these conditions shared in both Entry and Find mode? Remember that
the generated DESIGNER procedures are used both in Correct and
Change.</FONT></SPAN></DIV>
<DIV><SPAN class=516051416-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=516051416-24072007><FONT face=Arial color=#0000ff
size=2>Bob</FONT></SPAN></DIV>
<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
[mailto:Ken@Langendock.com] <BR><B>Sent:</B> July 24, 2007 12:08
PM<BR><B>To:</B> Deskin, Bob; 'Daniel Rodríguez';
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: New feature suggestion :
Fields with entry if and proceduresdesignerID<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=649090516-24072007><FONT face=Arial
color=#0000ff size=2>Bob, I understand your position. Break existing code is
a bad thing...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=649090516-24072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=649090516-24072007><FONT face=Arial
color=#0000ff size=2>I would LOVE an option in the Dictionary or on the
Qdesign statement that would generate numbered procedures with or without
the IF options.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=649090516-24072007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=649090516-24072007><FONT face=Arial
color=#0000ff size=2>Interdependencies may be a problem for some, but having
to write number designer procedures to simulate the same sequence as the
entry procedure is of a real pain to me.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=649090516-24072007></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT size=2>K<SPAN
class=649090516-24072007>en</SPAN></FONT></FONT></FONT><BR></DIV>
<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>Deskin, Bob<BR><B>Sent:</B> July 24, 2007 11:55
AM<BR><B>To:</B> Daniel Rodríguez;
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: New feature suggestion :
Fields with entry if and proceduresdesignerID<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2>The ENTRY IF generates the IF condition around the ACCEPT for the
field in the ENTRY procedure. The ENTRY procedure is generated and
processed in a linear manner. In other words, one field after another
in the same sequence as the fields appear on the screen. If the condition is
dependant on another field, it's quite easy for the developer to know
whether that field has been entered or not.</FONT></SPAN></DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2>Numbered DESIGNER procedures, on the other hand, can be executed out
of sequence. You can easily change fields in a different sequence than the
entry sequence. Inter-field dependencies can't be counted on in the same way
as they can during entry. This means that simply generating the IF condition
in a DESIGNER procedure might be more confusing.</FONT></SPAN></DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2>For inter-field issues, you can </FONT></SPAN><SPAN
class=295074015-24072007><FONT face=Arial color=#0000ff size=2>handle
them in the PREUPDATE procedure, where all inter-field relationships
can be verified. The alternative is to create numbered DESIGNER procedures
for the fields in question and have the DESIGNER procedures prompt
for all of the inter-related fields. While this could be generated
if the fields are linked by the same ID, often the fields are not related by
ID.</FONT></SPAN></DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2>Now I realize that you can argue this one both ways and that there
are many cases where simple conditions would work fine. However, once the
decision was made and a few years went by, any change would have potentially
affected many applications, so no change could be made.</FONT></SPAN></DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2>Bob</FONT></SPAN></DIV>
<DIV><SPAN class=295074015-24072007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE 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>
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>Daniel Rodríguez<BR><B>Sent:</B> July 24, 2007 11:34
AM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> New feature
suggestion : Fields with entry if and procedures
designerID<BR><BR></FONT></DIV>When you create a screen with fields with
the ENTRY IF option, you must write a procedure designer for the ID number
in order to obtain the same behavior in change mode than in entry
mode.<BR><BR>Is there any special reason for it or I'm missing something?
<BR><BR>It is possible that Qdesign autogenerate the code if the procedure
doesn't already exists?<BR><BR>Kind regards,<BR><BR>Daniel
Rodriguez<BR><BR><BR>SCREEN PRUEBA<BR><BR>TEMP TFIELD1 CHAR*2<BR>TEMP
TFIELD2 CHAR*2 <BR><BR>FIELD TFIELD1<BR>FIELD TFIELD2 ENTRY IF TFIELD1 =
"XX"<BR><BR>PROCEDURE DESIGNER 02<BR>BEGIN<BR> IF TFIELD1 =
"XX"<BR> THEN<BR> ACCEPT TFIELD2 <BR>END
<BR><BR><BR></BLOCKQUOTE></DIV>
<DIV> </DIV>
<DIV> This message may contain privileged and/or
confidential information. If you have received this e-mail in error or
are not the intended recipient, you may not use, copy, disseminate or
distribute it; do not open any attachments, delete it immediately from your
system and notify the sender promptly by e-mail that you have done so.
Thank you. </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>