10-16-2007 12:42 AM
I have a VB6 application that calls a remote function call in Sap and
was working properly until we installed a new gui patches / upgrades.
Now it will not logon to Sap. It blows up on this
If Not sapConnection.Logon(0, True) Then
bLogOn = False
End If
We tried replacing 3 files from the ealier version of the gui
(wdobapi.ocx, wdtfuncs.ocx & wdtlog.OCX). Then it logs on, but blows up
when it tries to call the function module in Sap:
theFunc.Call
I also tried replacing the librfc32.dll file in the c:\windows\system32
directory with the earlier version, but then I get an out of memory
error on:
Set functionCtrl = CreateObject("SAP.Functions")
Any ideas on how this can be fixed?
Thanks,
Bob
10-16-2007 1:18 AM
Hi Bob,
Have you checked if all passwords etc are Ok.
Also try to search in OSS there may be some note to fix it.
Regards,
Atish
10-16-2007 3:59 AM
10-16-2007 5:42 PM
10-17-2007 1:00 AM
I have an update. We discovered that one of the output parameters on the function module was declared as CHAR20. We redefined it to be use MCDATA-LINE. Now all the export parameters have real table names and fields in their type declaration.
We restored the 3 files from the ealier version of the gui (wdobapi.ocx, wdtfuncs.ocx & wdtlog.OCX). Now it logs on, and no longer blows up when it tries to call the function module in Sap using:
theFunc.Call
However, all the export parameters are empty. Using SE37 in test mode I know this is not the case, but everywhere I use:
theFunc.Imports("O_VAR"), where o_var is the exporting parameter
in the VB code to get the returned data, I have no values.
10-18-2007 7:23 PM