G
Guest
We have a VB front end application that calls into VBA code in Excel to
create report. The data for the report comes from a Sybase Database. The
data returned by Sybase looks good when running the stored procedure in
Sybase query tool.
When running through debugger in VBA code of Excel report, any number with a
trailing zero whether left or right of the decimal is dropped. So 20000
becomes 2, while 20000.01 stays 20000.01.
Number formatting of any kind is not working, because the result set already
has the truncated number.
The report used to work. The problem occurred once we moved to Windows XP
Pro. We have SP 1.
Right now, we are able to bypass this by adding .00001 to the number in the
stored Procedure - since we are rounding to .01, we can avoid the problem.
But still, has anyone seen this before or is this a known bug?
Any suggestions would be greatly appreciated. We have 20 more reports and
stored procedures to update and are looking for a better solution than adding
..00001.
Thanks.
John
create report. The data for the report comes from a Sybase Database. The
data returned by Sybase looks good when running the stored procedure in
Sybase query tool.
When running through debugger in VBA code of Excel report, any number with a
trailing zero whether left or right of the decimal is dropped. So 20000
becomes 2, while 20000.01 stays 20000.01.
Number formatting of any kind is not working, because the result set already
has the truncated number.
The report used to work. The problem occurred once we moved to Windows XP
Pro. We have SP 1.
Right now, we are able to bypass this by adding .00001 to the number in the
stored Procedure - since we are rounding to .01, we can avoid the problem.
But still, has anyone seen this before or is this a known bug?
Any suggestions would be greatly appreciated. We have 20 more reports and
stored procedures to update and are looking for a better solution than adding
..00001.
Thanks.
John