Thanks for the response, Cetin...

I know about the SQL limit but this process is building a Header string comprised of all the field-names in the Cursor concatenated together. This parameter is then passed to another procedure that does the actual Word document merge.

I cannot determine where the SQL limit applies here, or how I could split it up...apparently this Word OLE parameter string cannot be longer than 255? We have had to go in and actually shorten the field names ("CustomerName" becomes "Cname", etc.) to make it work...

-Irv.


>>Hello All:
>>
>>We have a Word OLE automation letter merge within VFP 6.0 that works well (most of the time). I am getting the following error currently:
>>
>>

>>Error number: 1429
>>Error message: OLE Dispatch exception code 0 from MS Word; String is longer than 255 characters.
>>

>>
>>This occurs during the create header source routine prior to the actual data merge, after Word object has been launched.
>>
>>Anybody seen this one and have any ideas? TIA,
>
>It's documented. For source SQL string can't be longer than 255 chars (word VBA problem not fox). However there is 2 SQL string parameters. Divide the string into 2 (first 255 in first) and put into 2 parameters.
>Cetin