Wdtlog.ocx
Norine Wiltshire
I'm using Sap Logon Control importing the activex component wdtlog.ocx to my non-sap delphi application. This activex comes with SAP GUI installation and my application is working fine. But I read this ocx was classic rfc library (librfc32.dll) dependent and this library is obsolete now. I also read that since SAP GUI version 7.50 this ocx is no longer classic rfc library dependent. Is this activex (wdtlog.ocx) SapLogonCtrl.dll dependent? Is wdtlog.ocx becomming obsolete? Or does wdtlog.ocx is totally independent now and I can use it for long?
Thank you for visiting SAP Community to getanswers to your questions. Since you're asking a question here for the firsttime, I recommend that you familiarize yourself with -and-answers (if you haven't already), as it providestips for preparing questions that draw responses from our members. For example,you can outline what steps you took to find answers (and why they weren'thelpful) and share screenshots of what you've seen/done. The more details youprovide, the more likely it is that members will be able to assistyou.
Should you wish, you can revise your question by selecting Actions, then Edit(although once someone answers your question, you'll lose the ability to edit thequestion -- but if that happens, you can leave more details in a comment).
I have now received the information from SAP that ActiveX controls such as SAP Logon Control (wdtlog.ocx), SAP Remote Function Call Control (wdtfuncs.ocx) and SAP BAPI Control (wdobapi.ocx) and their unicode versions which used the classical RFC library has been moved to the new SAPNWRFC. Technically from librfc32.dll to sapnwrfc.dll. SAP GUI for Windows 7.70 includes 64bit versions of these controls. Since these need sapnwrfc.dll, the delivery also includes a 64bit version of this dll.
In that case, you may make it work with DLLSurrogate, which will be supported long enough until SAP GUI 7.70 is officially released, as it will offer 64 bits controls -> You may save the following lines to a MakeSAPGUIRFC64bits.reg file and execute it as an administrator from Windows File Explorer to automatically update the registry values:
Does it make sense to use the "SAP Function Control" (wdtlog.ocx in connection with wdtlog.ocx and wdtaocx.ocx) to access (via the Interop-Assemblys SAPFunctionsOCX.dll, SAPLogonCtrl.dll and SAPTableFactoryCtrl.dll) to SAP with RFCs instead of the no longer supported SAP .NET Connector of .NET ?
SAP customers are quite notorious about "certified interfaces". If you use something that is not clearly supported by SAP then you should rather not use it. I think this applies for these controls: Aren't they part of the COM Connector that is no longer supported?