You could try turning your array into a cursor then using the CURSORTOXML function. Then RETURN the XML file, or store as a public variable in your object. You can then use the XMLTOCURSOR function at the other end to extract into a local cursor etc etc....
Yazster,
Sounds like an intermittent bug in the server code, could be a problem with accessing locked files or records too. Make sure each com server has an approroiate error handling routine, and an error log. Examining the error log may point you in the right direction.
Thanks Guys,
The Com servers have no interfaces which could pop up a screen or message so it cant be that. I am going to write a small server interface and de-bug on the server so i can see exactly whats going on. I'll let you know what the outcome was...thanks for all your help folks...much...
The client application just sits there, no OLE error messages or anything. I have to crash the client then manually close the COM object on the automation server.
I have created several COM servers which are installed on a Windows 2000 server(automation server). I can call the COM servers from my applications no problem and they work fine on local Data (held on the automation server). However, when i ask the COM servers to work on data on another machine...
I have created several COM automation servers which are installed on a Windows 2000 server. I can call the servers from my applications no problem and they work fine on local Data. However, when i ask the servers to work on data on another machine it all goes horribly wrong. The data is on a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.