We had to change the date format in order do some calculations.

 -* DEFINE BEGIN SDATE
SDATE/A8MDYY = EDIT (  PS_KV_PNCH_ANA_VW.PS_KV_PNCH_ANA_VW.PUNCHDATE , '99$99$9999' );
-* DEFINE END SDATE
-* DEFINE BEGIN SDATE2
SDATE2/MDYY = SDATE;
-* DEFINE END SDATE2 

Now that the parameter wants the date like this: 01012009

The javascript calendar added in html composer is no longer able to correctly populate the date fields as 01012009 is not one of the choices. The closes it has is 01/01/2009.

If the date fields are populated with the calender js they contain 01/01/2009 (slashes) and the report returns no data.

Is there a way to keep the date 01012009 format and still use the calendar js?

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

Just do a -SET at the beginning of your procedure with an EDIT to remove the slashes from the &variable. Probably several other ways as well.

quote:

Is there a way to keep the date 01012009 format and still use the calendar js?

How about thinking of it the other way around, keep the js as it is, with the slashes and just remove them in the WebFOCUS report? What do you mean "Now that the parameter wants the date like this: 01012009"? If the parameter passed from the launch page contains slashes, just remove them with Dialogue Manager:

-DEFAULT &DATE1 = '01/01/2009';

-SET &DATE1N = EDIT(&DATE1,'99$99$9999');

-TYPE &DATE1 &DATE1N

Use the corrected date variable in the report instead of the variable passed by the launch page.

Im close..

I added

-DEFAULT &START_DATE = '01/01/2009';
-SET &START_DATEN = EDIT(START_DATE, '99$99$9999');
-TYPE &START_DATE &START_DATEN
-DEFAULT &END_DATE = '06/30/2009';
-SET &END_DATEN = EDIT(END_DATE, '99$99$9999');
-TYPE &END_DATE &END_DATEN  

to the fex and now the start date will accept slashes. But the report still fails if the end date has slashes.

Does "Fails" mean it returns errors, or it is not returning the expected data? We would probably need to see how you use the &vars in your selection criteria and also know the actual format of the fields to which you are comparing those values in order to help you further.

Also (just noticed) that you are referencing field names in your -SET statements, which will not work. They must be &variable names:

-SET &START_DATEN = EDIT(&START_DATE, '99$99$9999');
-SET &END_DATEN = EDIT(&END_DATE, '99$99$9999');

quote:

Originally posted by Darin Lee:
Does "Fails" mean it returns errors, or it is not returning the expected data? We would probably need to see how you use the &vars in your selection criteria and also know the actual format of the fields to which you are comparing those values in order to help you further.

The report runs but it is empty as there are no date parameters.

quote:

Originally posted by Darin Lee:
Also (just noticed) that you are referencing field names in your -SET statements, which will not work. They must be &variable names:

-SET &START_DATEN = EDIT(&START_DATE, '99$99$9999');
-SET &END_DATEN = EDIT(&END_DATE, '99$99$9999');

That was it, its working.

Greg, I certainly hope there's an open WebFOCUS manual close at hand...