new.fex
----------------------------
DEFINE FILE DATE
ACDT1/I8YYMD=DATECVT(DATE,'YYMD','I8YYMD');
ACDT2/A8=EDIT(ACDT1,'99999999');
ACDT3/A6=EDIT(ACDT2,'999999$$');
END
TABLE FILE DATE
PRINT
DST.DATE
ACDT3
ACDT2
COMPUTE DT1/YYMD=DATEADD(DATE,'M',-2); AS DT11
COMPUTE DT2/YYMD=DATEMOV(DT1,'EOM'); AS DT22
COMPUTE DT3/A8=DATECVT(DT2,'YYMD','A8'); AS DT33
WHERE YEAR EQ '&YEAR'; -* this is line 145
WHERE ACDT2 LIKE '%01';
WHERE ACDT3 IN (&YEARMONTH);
END

--------------------------------------------

WHERE YEAR EQ ''2009'';
WHERE ACDT2 LIKE '%01';
WHERE ACDT3 IN (''200911'');
ON TABLE HOLD AS HLD
END
-RUN
(FOC1517) UNRECOGNIZED COMMAND GETTING THE DATE FOR THE REWARDS ISSUED.
0 ERROR AT OR NEAR LINE 145 IN PROCEDURE new FOCEXEC *
(FOC257) MISSING QUOTE MARKS: ''2009'';
BYPASSING TO END OF COMMAND
(FOC009) INCOMPLETE REQUEST STATEMENT

This message has been edited. Last edited by: Kerry,

Do you have any skill at debugging errors?

Add

-SET &ECHO='ALL';
-? &

to the top of new.fex - it looks like the value of one of the Dialogue Manager variables you're using in your WHERE statements is not what you think it is.

What is the contents of &YEAR ?, does it have quotes in it ?

Single quotes, NOT double quotes...

Tom, they are single, but two of them.

quote:

Originally posted by Francis Mariani:
Do you have any skill at debugging errors?

Add

-SET &ECHO='ALL';
-? &

to the top of new.fex - it looks like the value of one of the Dialogue Manager variables you're using in your WHERE statements is not what you think it is.

I am new to the WF tool.
I have already included -? & and -SET &ECHO = 'ALL';

quote:

Originally posted by Waz:
What is the contents of &YEAR ?, does it have quotes in it ?

I have selected 2009 as year from the launch page. So, &YEAR should get the value of 2009.

The ECHO should show you what values were substituted in the code. Post the execution of the code, get it by viewing the source from the web browser window.

Also the -? & will show all the variables and their contents.

quote:

Originally posted by Francis Mariani:
The ECHO should show you what values were substituted in the code. Post the execution of the code, get it by viewing the source from the web browser window.

The bottom part of the original posting is the execution of the code ......

Then your variable &YEAR has embedded single-quotes in it. Either get rid of those single-quotes or remove the single-quotes from the WHERE statement.

And what does

WHERE ACDT3 IN (&YEARMONTH);

do? That should probably be

WHERE ACDT3 EQ &YEARMONTH; 

Where did all those single-quotes come from? Why do you post the same questions in multiple postings?

Comparision Error between computational and alpha values

quote:

Originally posted by Francis Mariani:
Then your variable &YEAR has embedded single-quotes in it. Either get rid of those single-quotes or remove the single-quotes from the WHERE statement.

And what does

WHERE ACDT3 IN (&YEARMONTH);

do? That should probably be

WHERE ACDT3 EQ &YEARMONTH; 

Where did all those single-quotes come from? Why do you post the same questions in multiple postings?

Comparision Error between computational and alpha values

&YEARMONTH is a multiselection parameter.

quote:

(FOC1517) UNRECOGNIZED COMMAND GETTING THE DATE FOR THE REWARDS ISSUED.

Seems like the FOC1517 error may be caused by a missing comment marker (-*) for a comment line ("GETTING THE DATE FOR THE REWARDS ISSUED".

quote:

Seems like the FOC1517 error may be caused by a missing comment marker (-*) for a comment line ("GETTING THE DATE FOR THE REWARDS ISSUED".

It is fixed now but still getting that FOC257 error

As Francis said, this is because of the two single quotes that are wrapped around the Year or YearMonth.

It looks like you have single quotes embeded in the variable, therefore removing the single quotes arounf the variable in the code should fix the problem

quote:

Originally posted by Waz:
It looks like you have single quotes embeded in the variable, therefore removing the single quotes arounf the variable in the code should fix the problem

After removing the single quotes in the code.

WHERE YEAR EQ '2009';
WHERE ACDT2 LIKE '%01';
WHERE ACDT3 IN ('200910');
ON TABLE HOLD AS HLD
END
-RUN
16.42.26 AE SELECT T1."Date"(FORMAT 'YYYY-MM-DD')(CHAR(10)),
16.42.26 AE T1."Year"(SMALLINT) FROM WebfocusViews.DATE T1
16.42.26 AE WHERE (T1."Year" = 2009) ORDER BY T1."Date";
0 NUMBER OF RECORDS IN TABLE= 1 LINES= 1

Well then, it looks like we've fixed it.

When I select 2009 for Year and October for Month in the Launch Page
it should take the value of 2009 for &YEAR and 200910 for &MONTH.

should it be showing

-TYPE YEAR: 2009;
YEAR: 2009;
-TYPE MONTH: 200910;
MONTH: 200910;


OR


-TYPE YEAR: '2009';
YEAR: '2009';
-TYPE MONTH: '200910';
MONTH: '200910';

I am getting the later part in the execution.

P.S. I am new to the tool, It may be a silly Question.

You have too many DEFINE-based WHERE statements.

Why are you filtering on both the Year AND the Year/Month?

Most likely your WHERE statements cannot be passed to SQL (because they're on DEFINE fields) - this is why you don't see them in the SQL, but you should have warning messages regarding this.

quote:

I am getting the later part in the execution

I think you created your html launch page using the html painter. That would explain the quotes around the selected value, because that's the way the html painter returns the values. Should you have built the page outside of the html tool, then the way the values are returned would have been exactly as you built it.

This happenned almost to everyone! IBI should have fixed this problem that parameters passing down from launch page, autoprompt or drilldown shoud give us uniform values - either quoted or un-quoted.
Every time, it takes several twists & turns for all of us(young & old) to figure out, because we didn't EXPECT this behavior.

Hua