Wow, you know, this hit it right on the head... too simple and the simularities between the field names... I chased the wrong field all day.

Thanks!!!

>Hi Peter,
>
> I don't know why fQtyIn would be created as C(1), but I notice that field fPrnQty would be created as C(1). Are you sure it's not fPrnQty that's causing the problem? If product.qty is numeric then ctemp.fQtyIn should also be numeric.
>Have you posted the acutal code you use in your program in this thread?
>
>Hope this helps,
>Gavin...
>
>>I have a SELECT SQL statement as follows:
>>

>>vTempStr="sku as fSkuOur,desc as fDesc,price as fPrice,vend_id as fSkuVend,"+ ;
>>           "qty as fQtyIn,recno() as fRecno,'' as fPrnQty,price as fPrnPrice "+ ;
>>           "from product into cursor cTemp "
>>select &vTempStr
>>

>>
>>Everything appears to be working fine except for something I stumbled on by accident today....
>>
>>The PRODUCT.QTY field is a numeric
>>
>>the CTEMP.FQTYIN field is being set as character length 1
>>
>>Not sure why or how this is happening, and in most cases it is working fine EXCEPT when I have qty amounts larger than 9 (1 single digit)... then of course the extra digits are being dropped.
>>
>>I need to figure out why, and how to correct it... I need those larger figures.