Well, I am glad my answer helped (or perhaps you had figured it out by yourself, in the meantime?)

Where I used type conversion, mainly, was when inserting into Excel fields. When inserting a currency value into a field (through Automation), Excel will add the currency symbol, which is not always what I want. In this case, the mton() conversion is usually appropriate.

>Sorry for the late response Hilmar
>That's exactly what I did. When I created the table, I added a couple of fields "space(5) as somevar" and used the replace command to fill those fields as character representations of the numeric fields.
>You are the first and only person after a month of questions to come up with the answer that works. Even Microsoft has ignored the request for an answer to that issue.
>
>Thanks again for the help.
>
>
>>>I am using vfp7 sp1 to merge data with a word2000 document. The doc merges with vfp data. The doc file has a database inserted. When the doc is printed the amount field does not print correctly if zero's are present as in: 250.50 prints as 25 . , 255.00 prints as 255 but 276.35 prints correctly and so on...I can't figure out a way to format that field. the field is n(12.2).
>>
>>As a workaround, perhaps you can create a version of the DBF, where you convert the numbers to character, before transferring to Word?
>>
>>>The doc insert code is:
>>>

>>>{DATABASE  \d "U:\\Finacct\\Source\\v7PropNums_ver1.00\\Data\\memodata.dbf" \c "DSN=FoxPro Files -
>>>Word;UID=;PWD=;SourceDB=U:\\Finacct\\Source\\v7PropNums_ver1.00
>>>\\Data;SourceType=DBF;Exclusive=No;BackgroundFetch=No;Collate=MACHINE;Null=
>>>Yes;Deleted=Yes;" \s "SELECT nproperty as '. Property Number .', descrip as
>>>'.                             Description                             .',
>>> acqcost as '.    Cost  .', serialno as '.  Serial Number  .' FROM
>>>memodata.dbf ORDER BY `nproperty`" \l "2" \b "63" \h}
>>>

>>>This displays that data queried but the amount field "cost" does not display zero's. Any ideas?
>>>
>>>Chuck