Skip to Content
0
Former Member
Jun 16, 2006 at 06:11 AM

GUI Scripting Engine Type Mismatch

337 Views

Hello everyone,

We've got an external CRM system that invokes a (relatively!) simple piece of Visual Basic 6 code that uses SAP GUI Scripting to invoke VA01, fill in the details on the first screen, and then put the relevant Sold To number on the next screen. When the user saves the order, the VB6 app reads the message and extracts the order number, storing it in the CRM system.

We've just installed everything on a new PC, and the scripting doesn't work on it. I have created a debugging version of the VB6 program, and it is executing the lines:

Set oSAPGui = GetObject("SAPGUI")

Set m_oGuiApp = oSAPGui.GetScriptingEngine

The second line is coming back with a Type Mismatch error (Err.Number 13 in VB6)

The app server is definitely okay - it is working for other people and I checked using transaction RZ11 just to be sure.

The SAP GUI Front End seems to be okay - I went to the options under "Scripting -> User Settings" and it says "Scriptng is installed!" and the "Enable Scripting" checkbox is definitely checked. I've checked wdtfuncs.ocx, and it's registered - I registered it again anyway - and comparing the C:\Program Files\SAP\SAPgui\FrontEnd directory with a PC that it does work on shows no differences apart from a wdtfuncs.oca on the working PC, and a "changed" wdobapiU.ocx and wdtlogU.ocx (for which the versions are the same anyway).

We are using VB6, and we have SAP GUI 640 FInal Release, File Version 6403.3.11.2963, Build 760892, Patch Level 11