>>Hi Cetin
>>
>>add following lines to your LOAD event (your initial example message#1407791)
>>

>>SET FIXED ON
>>SET POINT TO ','
>>

>>
>>and try again.
>>
>>Seems the comobox does internal transforms
>>
>>alter .COLUMNWIDTHS to "180,100" to see the problem
>>
>>Agnes
>>
>>>Cetin,
>>>
>>>there is something that is changed by a SET command or the like. It's a SET that is limited to a datasession. In the moment I try to figure out what.
>>>
>>>(If I do not load my defaults of the SET then it works as you have suggested)
>>>
>>>I will post my results here
>>>
>>>Agnes
>
>Well in 25+ years with fox I didn't know what "set fixed" does. Now I know - trouble maker:) Sorry I don't know how you can fix < g > with set fixed on ( looks like a bug to me - VFP SP1).
>Cetin

We have data with common decimal precision of 3 but display them anywhere with a precision of 1. This is customers wish. So

SET DECIMALS 1
SET FIXED ON

will bring every textbox, combobox, listbox, spinner and report field to display the 1th decimal only.
As soon as you set the focus on an object you will get all 3 decimals.
(It also will feed the support, since totals can not be added up by single lines (^.^) )

SET POINT ','

is german standard.

The solution to fix the problem is simple:
Translate the integer keys to char (using PAD?, CAST or CTOBIN) and work with them.
The CA will replace the integer FK with the altered character, this is something I do for years.

(Since as mentioned earlier numeric keys will not work for me. (giggling))

What do you mean with VFP SP1? It's there as long as I code VFP. Must be a feature to keep germans working.

Agnes