>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.

Unfortunately, *every* error returned by Automation (once you have a valid connection to the server) will be 1426, 1427, 1428, or 1429. There's little difference in the types of errors that can be funnelled back for any given error number-- 1426 can return "Unknown name" (likely meaning you've misspelled the property name--ignore through and the rest should run fine), to "The RPC server is unavailable" (meaning something drastic has happened to your server and ignoring through ain't gonna work). You'll need to look at the MESSAGE() or the third position in the AERROR() array to determine what to do.

As for simultaneous connections, as in:

oExcel1 = CreateObject("Excel.Application")
oExcel2 = CreateObject("Excel.Application")

There *is* a difference between how '97 and 2000 handle multiple instances of the application object. 2000 handles it nicer than 97, which may be why your one client is experiencing problems. My recommendation is to open ONE instance of the Application object, and TWO instances of the Workbooks objects, as in:

oExcel = CreateObject("Excel.Application")
oWorkbook1 = oExcel.Workbooks.Add()  && Or use Open(), whichever is needed.
oWorkbook2 = oExcel.Workbooks.Add()  && Or use Open(), whichever is needed.

Now you can hop back and forth between Workbooks with no problem. With this approach, I didn't have problems in 97.

Hope this helps,

- della Martin