Same issue with a more simple expression like: DVal ( '01/01/2016',
toggle quoted messageShow quoted text
Maybe XPA stopped using the Magic (Integer) Date format internally?
Or it is simply a bug of how it sends parameters to a DirectSQL?
On 18/1/2017 8:07 πμ, Avgerinos wrote:
Correcting the typo:
DVal (DStr ( '01/01/2016'D, 'DD/MM/YYYYY'), 'DD/MM/YYYYY' ) )
On 17/1/2017 10:29 μμ, Avgerinos
Documenting some difference in behavior I noticed while
migrating from uniPaaS to XPA3 (tested on 3.1.b so far).
Expression DVal (DStr ( '01/01/20616'D, 'DD/MM/YYYYY'),
'DD/MM/YYYYY' ) ) is sent as a parameter to an DirectSQL
I use the SQL Profiler to see how this finally evaluates:
It's messing up all programs that use direct SQL, since they all
base on date filtering.
- in uniPaaS it evaluates as number 735964.00000000 (the
integer behind a MagicDate) and works fine.
- in XPA is evaluates as number 160101 and brings wrong
Any known workaround or global setting, so that I avoid
correcting programs with Direct SQL one by one?
Thanks in advance