>>>Or is it just displaying it the wrong way? Try to Set Decimals to 10 or so, and see if it's just the visual representation that's wrong.
>>
>>
>>Hello again. Thanks for trying to help me here. I tried what you said, "setting decimals to 10" and it still will not work. There seems no way to bind this a VFP combo control to an integer field. Anyone else out there have a work around?
>
>I use integers in combos all the time, but then the rowsource is practically always fields, i.e. "alias.displayfield,integerkey", and these integers are usually small and surely not negative. I wonder if large negative integers may somehow be out of scope for Fox? I assume the definition of large would be "negative with the 31st bit used". This is not the only place where VFP's definition of integer as "signed 32-bit integer" doesn't really work; it's also when you try to use some APIs which need large unsigned integers (with 31st bit set) that we have problems.
I tried an experiment. I changed my customer ids to 1,2,3,4,5 etc. changed the coresponding custids in my orders table. Reran the form and it worked! Then I used large integer values like 2147483644. The combobox stoped working again. You must be correct. I'm not sure where the cut-off is but at some point VFPs conversion to numeric (Large integers) the conversion starts to use powers in it's representaion of numeric data.
Thanks for all your help!
Thanks in advance or I hope this helps!
[STS]
:>