![]() Shell ("C:\Program Files (x86)\SAP\FrontEnd\SAPgui\saplogon.exe") I found your other helpful link here which I meshed with your recommendations above to come up with this.ĭim SapGuiAuto As SAPFEWSELib.GuiApplication With the modification in the registry I can instantiate the class, but I can't call the method OpenConnection or OpenConnectionB圜onnectionString successfully. I build a new environment without any modifications on the registry and the following code works without any problems in 64-bit VBA: Sub Test()īut if I call Set SAPguiAPP = CreateObject("Sapgui.ScriptingCtrl.1") It seems that is not necessary to modify the registry for this kind of programs. In my case a normal script works without any problems in 64-bit VBA with the actual SAP GUI for Windows: Sub Test() Here is my current reference setup.I don't think the ActiveX DO reference is necessary.I was just trying a few things. Not sure if that would cause this not to work.Īs per your thread, is the declaration. Again, the key was automatically added to the HKey_Local_Machine area. To be certain, I deleted everything and did it again, paying close attention to which HKey area I was in. It was if if the key I added under HKey_Classes_Root\Wow6432Node\AppID\ was automatically replicated. When I went to add the new key under HKey_Local_Machine\Software\Classes\AppID\ the key with the name of the COM object GUID was already there (and already contained the DllSurrogate string). One thing that didn't go as per the instructions. Here is what my registry currently looks like. Set SAPguiAPP = CreateObject("Sapgui.ScriptingCtrl.1") Unfortunately, I'm still getting the 429 run-time error at. ![]() I implemented Emmanuel Carabott's registry hack, rebooted, and tried to login to SAP from Excel VBA. Thank you very much for your consideration, If you do indeed decide to create a blog post or document on this topic or know somebody that will be able to help us, please let me know by responding to this post (I am now following it). Microsoft ActiveX Data Objects 6.1 Library ** run-time error 429.ActiveX component can't create object Set Connection = SAPguiAPP.OpenConnectionB圜onnectionString(IP_Address) Set SAPguiAPP = CreateObject("Sapgui.ScriptingCtrl.1") ** Public Connection As SAPFEWSELib.GuiConnection Public SAPguiAPP As SAPFEWSELib.GuiApplication Here are some snippets (functional in the 32-bit environment). From the content of your blog posts, it appears that you very likely have some knowledge to share with the community on this topic. We recently brought in a system running 64-bit Office and can't figure out how to configure VBA to open a connection to SAP. The GuiInputControl class has never been documented too and the renamed class GuiInputFieldControl is actually also not completely documented too. The renamed class GuiComboBoxControl is actually also not completely documented. Hint: I detect the GuiListControl class at the SAP GUI 7.30 PL6, you can find more information here. If you use this controls in your SAP GUI Scripting programs, be careful if you update to PL7. GetHistoryEntryText (In ISapInputControlTarget As Long) As WString It is the same with GuiInputControl and now GuiInputFieldControl.Īs far as I can see the methods SetInputControlText (In ISapInputControlTarget As WString) As Integer.SetInputControlText (In ISapListControlTarget As WString) As Integerĭoesn’t exists anymore and the method FireSelected () GetTextFromID (In idVal As Long) As WString It seems that the GuiListControl is now renamed to a GuiComboBoxControl with different methods.Īs far as I can see the methods SetSelectionID (In i As Long).$CLSID_SAPFEWSELib_GuiListControl = GUID$("") With this patch level 7 SAP offers also a new version of the SAP GUI Scripting API (sapfewse.ocx). ![]() Since four days offers SAP a new patch level of the SAP GUI for Windows.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |