General information
Category:
COM/DCOM and OLE Automation
>Use CreateObject() instead of CreateObjectEx().
I can't use CreateObject() because the object (DLL) is deployed only on one machine (the server).
>What errors do you get back?
No error is reported; simply after a period of time (about 30 seconds, the same time that other clients (Windows98 - NTWorkstation) use to successfully load the DLL and send the results), the operation ends with no effect.
>Did you run the Client install on the XP box?
I don't know about Windows XP, which I found installed on the new machine. That was my first approach with XP.
Can you give me other information about 'Client install on the XP box'.
TIA
Bruno Maddalozzo
>Some time ago I built a DLL (in-process server), installed as a package under Microsoft Transaction Server on a "server" machine running Windows NT Workstation, which queries a Pervasive Database using ODBC.
>The program (a VFP6 exe), deployed on the same machine, calls the DLL with the statement:
>CREATEOJECTEX(...) and all works fine with clients, calling the program, running Windows 98 or Windows NT Workstation.
>
>Now, we have connected a new client, running Windows XP Professional, but this one doesn't work, when trying to access the DLL. It seems like if it couldn't instantiate the DLL.
>
>Can you give me any tracks to solve the problem?
>Many thanks.
>Bruno Maddalozzo
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only