Hi,
we have changed to TD6.0/SP2 and delivered to our customers(SP3 not working because COM-troubles, but the same mistake!!!). Since we have converted to Unicode-Version, we have massive troubles with SalFmtFormatNumber. You can see an example at the attached picture.
The source-code behind is:
Set sFmtSaldoKst = SalFmtFormatNumber (nKST_Saldo , '#.##0,00\' S\';#.##0,00-\' H\'')
Or simple
Set sFmtSaldoKst = SalFmtFormatNumber (nKST_Saldo , '#.##0,00 ';#.##0,00-'')
Now we have written a work-around like
Set sFmtSaldoKst = SalFmtFormatNumber( nKST_Saldo, '#.##0,00;#.##0,00' ) || StrIFF( nKST_Saldo, '-H', ' S', ' S' )
We have hundred lines where we must changed this, and this code is working since 1992.
Windows Vista/Windows 7 32bit / 64bit and German/Austria-Version!
See also the entries from my colleague Andreas in TD5.2 forum.
Best regards,
Michael
SalFmtFormatNumber
SalFmtFormatNumber
You do not have the required permissions to view the files attached to this post.
Re: SalFmtFormatNumber
I see nothing new in our TD defect database that is reported new for SalFmtFormatNumber. We need a test case.
Set sFmtSaldoKst = SalFmtFormatNumber( nKST_Saldo, '#.##0,00;#.##0,00' ) || StrIFF( nKST_Saldo, '-H', ' S', ' S' )
I'm missing something here! And it may be more than a test case
That's a Report Builder function. How is it you can mix a TD SAL function + a RB function like you show:StrIFF
Set sFmtSaldoKst = SalFmtFormatNumber( nKST_Saldo, '#.##0,00;#.##0,00' ) || StrIFF( nKST_Saldo, '-H', ' S', ' S' )
I'm missing something here! And it may be more than a test case
Re: SalFmtFormatNumber
Hi,
we don't use Report Builder. This effect is also at Table-Windows, DataFields ....
See the example in TD5.2 from Andreas.
Michael
we don't use Report Builder. This effect is also at Table-Windows, DataFields ....
See the example in TD5.2 from Andreas.
Michael
Who is online
Users browsing this forum: [Ccbot] and 0 guests