RE: Max String Character for SQL in SP5

Hi, Eskil,

the reason for the change is the existence of NULL and NaN values in SQL 
databases, which do not exist in the Native database.
If a SQL query performs a comparison against these special values, the 
result will be false.

If you think, that the usage of the new maximum characters has not been 
implemented correctly throughout the kernel, then I kindly ask you to send 
the description with a reproduction scenario to the XAL support, so that the 
report gets verified officially.

Thank you very much in advance 
Hannsjörg Zdarsky
Software Design Engineer
Microsoft Deutschland GmbH


"Larsson Eskil" wrote:

> The character used for filling out empty searchfields has been changed
from
> ASCII 255 to 253., for SQL.
> This does not work in Forms like CredPurchaseStat, but works alright in
> Qtx'es.
> 
> What is the reason for this change. I can't find any documentation on this
> change.
> 
> /Eskil
> 
> 

Hi,

so that's the reason for some wrong values in reports especially in
accounting. When there is a box where you enter a "centre" and you do
not enter a value for the "to"-field, then all transactions with a
centre given are ignored and the results are wrong. I mean, my own
work-around is to fill the fields with "9999999999" and the results
are the right ones...

Is it better to change the Macro MaxStr to how it was in older
versions to make sure results are right?