V11 date problem

[pauldb]

Existing RSW report that run just fine in v10. ____In the report I have a ParameterRR field which is a DATE.__When the report runs, the parameter Entry screen is presented to the user without a date being already pre-entered.__When the user chooses a date with the date-picker button, this date returns in the wrong format. Instead of being in the regional DD/MM/YYYY format, it is MM/DD/YYYY.__When the report runs, no records are selected. ____If the user does not use the date-picker, but enters the date manually in the correct DD/MM/YYYY format, same result: empty report. ____I went into the report, edited the parameterRR field.__When I choose a default value in the Edit ParameterRR Field window, by using the datepicker, the returned date was again MM/DD/YYYY. Wrong again, and when pressing OK on the window, I got an error message "Unrecognized name or operator"____So I manually entered a default date in DD/MM/YYYY format which was accepted.____And guess what, when running the report, it worked now. The user could even choose another date in the parameter Entry screen and it would still work. __________

[kfleming]

I will see if I can reproduce this problem and if so will have it corrected by development. In our testing we did try both mm/dd/yyyy and dd/mm/yyyy default reports and we thought that both worked but I will go back and re-test.____Kathleen__R&R Support

[pauldb]

>I will see if I can reproduce this problem and if so will __>have it corrected by development. In our testing we did try __>both mm/dd/yyyy and dd/mm/yyyy default reports and we __>thought that both worked but I will go back and re-test. __>__>Kathleen __>R&R Support ______Kathleen, ____how far are you on this one?__This is becoming VERY URGENT. It seems that about everything in V11 that has to do with date selection is broken!____As a result a lot of our applications are not working anymore. They just print empty reports. These are the reports in which the date range is set by the application itself, e.g. ____cFilter := ^INRANGE(RODatVan, CTOD("12/07/2004"), CTOD("31/12/2004") ) ^__SetFilter(hReport,String2Psz( cFilter))____The same goes for reports in which the user can define his own query. When picking dates with the datepicker, it doesn^t work, dates are returned in the wrong format.____When can we expect a fix please? ____Paul______________

[pauldb]

and can the webmaster of this forum check why there are emotions icons popping up all over the place when I use certain characters ??____Paul

[pauldb]

Liveware "support" please react!__Question is one week old now. ____When can we expect a fix for date problems. This is very urgent.

[kfleming]

We are working to correct the international date problem and it should be available in the next 11.0.007 update.______Kathleen__R&R Support

[pauldb]

Kathleen when is this appr. to be expected? __Would you like me to test it first? __if so send me the build____Paul

[kfleming]

I re-tested the date problem and the only problem that I am seeing is with the calendar date selector when the report format is dd/mm/yyyy.____I am able to successfully use a filter clause that says:__Datefield=ctod("06/03/2000")____and for my EuroDate report I get back records for March 06 2000.____This same filter in my USDate report gives me June 03 2000 records.____I can also set the Filter to a ? to display the filter dialog. if I select from the calendar, the date is incorrectly transposed in the EuroDate report but if I manually enter 06/03/2000, in the EuroDate report I get my March 06 2000 records and for the USDate report, I see the June values.____Kathleen__R&R Support

[pauldb]

Kathleen,____I^ve re-tested everything.____It works indeed a bit better than I first thought but only when paying much attention.____So the datepicker is broken, it always returns a date in US format.__The user must remember that he MAY NOT use the datepicker. __However, when he types in the date manually in European format, it works and he gets the correct set of recs. ____But: even when he types in the date correctly in a parameterRR field dialog box, he must now press a button "Modify" after having typed in the date ... if he doesn^t and just presses OK, RR will run the report but ignore the entered date. __Maybe the v10 behaviour was more logical (with the Accept/Revert buttons).__I didn^t notice this change at first, so when users said they got empty records, I assumed it was because of the date problems. In reality it^s a modified ParameterRR dialogwindow...(in combination with the broken datepicker)____As for setting the daterange programmatically with a Filter clause: weird; it works indeed. ____So it is less urgent than it seemed to be. ____Paul____________

[kfleming]

At least we are in synch on the extent of the date problem.__We are working on the date selector and are also in the process of making some overall parameteRR dialog changes. So I want to think that better things are on the horizon.____Kathleen__R&R Support