S
slacroixak
Guest
>for some strange reason progress likes the dates to be MDY 
- See more at: community.progress.com/.../76234 Marian Hi Marian, this is a dangerous trap... you should use the QUOTER function for date, datetime and decimal data types in order to accomodate this kind of problem. I mean, when a date appears between double quotes in a dyn query, the the ABL knows how to take your session non american culture (date format, numeric decimal point) into account Note QUOTER was introduced a long time ago (V9 days) to solve this issue. QUOTER also takes care of the unknown value. (returns unquoted question mark character in that case) Combined with the good SUBSTITUTE function, the solution becomes: pQuery = SUBSTITUTE("Fecha >= &1 and Fecha <= &2", QUOTER(date1), QUOTER(date2)). where date1 and date2 are of DATE data type. I mean, if the point of your get4GLDate() is to return a date in MDY, then I believe this is a wrong track. HTH Kind regards /Sebastien L.
Continue reading...
- See more at: community.progress.com/.../76234 Marian Hi Marian, this is a dangerous trap... you should use the QUOTER function for date, datetime and decimal data types in order to accomodate this kind of problem. I mean, when a date appears between double quotes in a dyn query, the the ABL knows how to take your session non american culture (date format, numeric decimal point) into account Note QUOTER was introduced a long time ago (V9 days) to solve this issue. QUOTER also takes care of the unknown value. (returns unquoted question mark character in that case) Combined with the good SUBSTITUTE function, the solution becomes: pQuery = SUBSTITUTE("Fecha >= &1 and Fecha <= &2", QUOTER(date1), QUOTER(date2)). where date1 and date2 are of DATE data type. I mean, if the point of your get4GLDate() is to return a date in MDY, then I believe this is a wrong track. HTH Kind regards /Sebastien L.Continue reading...