I think that is a pretty clever idea and something I will want to look at. I had been playing with storing the STR value off to a text column and having and update trigger on the backend translate that to SQL decimal(22,10)
Thanks
>>>>>>>>Any help ?
>>>>>>>
>>>>>>>Have you tried N(33,10) in VFP ?
>>>>>>
>>>>>>Create table testit (mynumber n(33,10))
>>>>>>
>>>>>>gives an error that "field width or number of decimal places is invalid"
>>>>>>
>>>>>>In the table designer the best I can get is 20,9
>>>>>>
>>>>>>Am I missing some trick?
>>>>>
>>>>>Sorry, have you tried B(10) ?
>>>>
>>>>Yes, and B(16)
>>>>
>>>>Both store 123456789012.12350000
>>>
>>>Did you check VFP Help Double Type?
>>
>>Again, yes. Double stores the number as 123456789013
>>
>>As Al and HIlmar have confirmed what I am seeing is a limitation of VFP.
>
>Have you tried shifting the decimal point? You could multiply by 100000 to shift the decimal point left for storing and then when retrieving divide back by 100000 for calculations. The number that you multiply/divide is determined by the number of significant digits that you want to maintain.
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.
