Thanks for getting back to me, Larry. It took a while to respond, as I was doing more research on this problem. The article to which you refer does not seem to apply, however I think I found the problem, and this is more of a question, too.

I'm using Excel 2000 on my development system, and the client has Excel 97. My program was setting up two simultaneous connections with Excel, and it appears that Excel 97 experiences some kind of a conflict with this. Even though I am indeed fully-qualifying the Excel object, there will appears to be conflict.

Therefore, my question is: Is there a difference between Excel 2000 and 97 that would cause this sort of difference concerning multiple connections?

This is the only cause I can think of for my program's errors, but the client has not tried out the update yet. However, there were two different processes taking place with Excel, one used one connection at a time, and the other used two connections at a time. It was with the multiple connection process that the client was having trouble. I changed the mutli-connection to a sequential connection, and am awaiting feedback from the client.

Thanks!
Michael Reynolds


>Michael,
>Check out MSKB Article Q178510. It seems to apply.
>
>HTH.
>
>>Greetings,
>>
>>I'm at a loss of how to resolve an error a client periodically experiences, which I cannot duplicate on my system.
>>
>>The application is programmatically constructing an Excel spreadsheet and there is a particular area where data is being sent to cells. The odd thing is that a number of methods are being used to send various data to cells, but it is only this one place which is causing the error.
>>
>>The section of code starts like this:
>>
>>

>>LPARAMETERS poExcel, pnRow, pcPhone, pdActivationDate, ;
>>   pdTerminationDate, pnDays
>>
>>poExcel.Cells(pnRow,  1) = pcPhone
>>poExcel.Cells(pnRow,  2) = pdActivationDate
>>poExcel.Cells(pnRow,  3) = pdTerminationDate
>>poExcel.Cells(pnRow,  4) = pnDays
>>.
>>.
>>.
>>

>>
>>The process of sending data is no different than other areas, but this place is causing the following error:
>>
>>Error# 1426, OLE Code 0x800203ec Unknown, Com Status Code
>>
>>According to the HELP system, it simply says:
>>
>>OLE error code 0x"name" (Error 1426)
>>You have received an error code from OLE (in hex), and a brief description of the error. The remedy depends on the error returned by OLE.
>>
>>Does anyone have an idea what could be causing this error? It's very frustrating, and the client of course wants it eliminated. Ignoring the error and letting it resume does not appear to cause any trouble, so I'm considering trapping the error and doing RESUME NEXT. However, I'd like to know what is causing it.
>>
>>Thanks!
>>Michael Reynolds