I am hoping some of the serious math wonks will take pity on an old man who still finds long division challenging.
I have SQL database tables that make heavy use of floating point numbers.
In my remote view, I am pulling half a dozen of those numbers. The remote view defines them as data type 'B' ( of which I have not previous experience)
I need to multiply those number together, then put the result in a field I created as part of the remote view ( casting a 0 as float )
But in the watch window these values all show up as N , even though the values can look like 140333030.002033021000
And when I multiply them the result looks like a float, But when I try to save the value into a view column, I get a numeric data overflow.
Trying to cast the numbers as B just gets them lopped off after about 4 decimals. ( I think this has something to do with 16bit vs 32 bit math, but since my brain runs on an i386sx chip, it is beyond me )
I'm sure this problem is nothing new to anyone who has tried it and I found this
http://fox.wikis.com/wc.dll?Wiki~VFPFloatingPointDataTypeon the wiki.
But I am trying to wrap my brain around how to employ conversions ( and which of the functions to use ) in pulling, manipulating and hopefully saving the data.
Really stuck on this one.
TIA
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
