invoking LC webservices from VB6 where "invoke" is reserved word

[Former Community Member]

Hi everyone:

I'm making some poceses tests on one customer (We are running a proof of concept and  positioning LC technology ) who wants to invoke LC PDF-G orchestrated services using the WS endpoint from an VB6 app.

When the VB6 app creates the proxy object to call the invoke method  exposed by the LC orchestrated process an compilation error occurs,
apparently invoke is a "reserved word" for internal use in VB6, so it doesn't works...

If we try to invoke an out-of-the-box LC service from a VB6 app via the WS API all works fine!

This is part of our code:

SERVICE = ""

Port = ""

'  ----------------------

WSDL = "http://172.26.45.195:8080/soap/services/getReportTitle?WSDL"

'  ----------------------

Set objSoap = New  MSSOAPLib30.SoapClient30

objSoap.ClientProperty("ServerHTTPRequest") = True

Call objSoap.MSSoapInit(WSDL,  SERVICE, Port)

objSoap.ConnectorProperty("AuthUser") =  "administrator"

objSoap.ConnectorProperty("AuthPassword") =  "password"

Resultado =  objSoap.Invoke("1")

An we attache the VB error.

How to solve this problem...??

Thanks in advance,

Diego.

[Hodmi]

That's going to be tricky because any custom LC processes has a default method of invoke.  You may be able to "reflect" it by creating a java service that lives on the LC server.  That java service can call the LC application and could be called by the VB6 app.

On the other hand, I though Microsoft end-of-life for VB6 was back in March 2008 - so you may want to push them into using a .Net version.