Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hello all,
Our Windows project (written in C++) makes heavy use of Excel by writing values to and reading them from Excel files via C++ wrapped database calls. Now the problem is this. If I, for example, type the floating point value 19.1 into a cell and then read it from the cell, I get garbage like 'F1' or even a date such as "January 19". Integers work fine, but floating point values always come out as garbage. It would seem that, for some reason, Excel insists on reinterpreting our floating point values regardless of whether the cell is configured as a floating point number, a string or whatever.. =( To make things worse. Different computers / different Excel installations yield different results. Is there a way to stop Excel from messing with our floating point values? Thanks for any helpful replies! Regards, Markus |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
2008 Australian Excel Conference - March 12 - March 14, Sydney, Australia | Excel Discussion (Misc queries) | |||
2008 Australian Excel Conference - March 12 - March 14, Sydney, Australia | Excel Discussion (Misc queries) | |||
2008 Australian Excel Conference - March 12 - March 14, Sydney, Australia | Excel Worksheet Functions | |||
2008 Australian Excel Conference - March 12 - March 14, Sydney, Australia | Excel Discussion (Misc queries) | |||
2008 Australian Excel Conference - March 12 - March 14, Sydney, Australia | Excel Discussion (Misc queries) |