Hello Harjyot,
first of all a happy new year.
I need to simulate your environment, because don't have one. So I code a POS simulation library, here the source:
'-Begin------------------------------------------------------------
'-Directives-----------------------------------------------------
#Compile DLL
Option Explicit
'-api_GetTerminalParams------------------------------------------
Function api_GetTerminalParams (_
ByVal ptrszTerminalID As Dword, _
ByVal ptrszRetailerID As Dword) Export BDecl As Long
Poke$ ptrszTerminalID, "12345678" & $Nul
Poke$ ptrszRetailerID, "0123456789ABCDEF" & $Nul
api_GetTerminalParams = 1
End Function
'-End--------------------------------------------------------------
There is only the function API_GETERMINALPARAMS in BDecl declaration, which means Pascal.
As you can see I write the IDs to the given addresses.
To check it out I code a VBScript, here the source:
'-Begin------------------------------------------------------------
'-Directives-----------------------------------------------------
Option Explicit
'-Main-----------------------------------------------------------
'-Variables----------------------------------------------------
Dim DX, rc
Dim TerminalID, strTerminalID, ptrTerminalID
Dim RetailerID, strRetailerID, ptrRetailerID
Set DX = CreateObject("DynamicWrapperX")
If IsObject(DX) Then
strTerminalID = DX.Space(9)
ptrTerminalID = DX.StrPtr(strTerminalID, "s")
strRetailerID = DX.Space(17)
ptrRetailerID = DX.StrPtr(strRetailerID, "s")
DX.Register "C:\Dummy\POS.dll", "API_GETTERMINALPARAMS", _
"i=uu", "r=l"
rc = DX.API_GETTERMINALPARAMS(ptrRetailerID, ptrTerminalID)
TerminalID = DX.StrGet(ptrTerminalID, "s")
RetailerID = DX.StrGet(ptrRetailerID, "s")
MsgBox "TerminalID: " & TerminalID & " RetailerID: " & _
RetailerID
Set DX = Nothing
Else
MsgBox "Can not create DynamicWrapperX object"
End If
'-End--------------------------------------------------------------
It works as expected.
To your question:
It is not necessary to configure the SOLE transaction. OLE access via ABAP works without this configuration. That's history I think. Other configurations are, as far as I know, not necessary.
Error 2 means incorrect function call. Look at the example codes of your POS library as they are called, I don't know it.
Be sure that you register DynWrapX.dll correct. You must have admin rights on your presentation server to use regsvr32 dynwrapx.dll in the command line.
My tip:
Try to use the functions via DynamicWrapperX from your POS library on your presentation server via VBScript first, like above. It is easier to find the correct way and it is very easy to port it to ABAP, as you can see.
Let us know the results.
Good luck.
Cheers
Stefan
- SAP Managed Tags:
Hello Marcelo,
your link doesn't work.
Cheers
Stefan
- SAP Managed Tags:
Hi Stefan
I tried to follow your example to test my VC++ dll but failed, could you please help to have a look? Thank you very much
- Developer a VC++ DLL ,Compile the solution and generate the DLL file
2. Copy the DLL_Tutorial.dll and dynwrapx.dll to a local folder
3. Register dynwrapx.dll
4. Run TCode SOLE to add OLE application
5. Tried to call DLL_Tutorial.dll but failed
report z_testdll.
include ole2incl.
"-Variables------------------------------
data Win32 type ole2_object.
data ret type i.
CREATE OBJECT Win32 'DYNAMICWRAPPERX'.
CALL METHOD OF Win32 'Register'
EXPORTING
#1 = 'c:\work\DLL_Tutorial.dll'
#2 = 'Add'
#3 = 'i=ll'
#4 = 'r=l'.
CALL METHOD OF Win32 'Add' = ret
EXPORTING #1 = 6 #2 = 8.
write ret.
free object win32.
Best regards
James
- SAP Managed Tags:
Hello James,
welcome to this forum and thanks for your reply.
At first, to retrace your error, I create a C similar library to yours:
; Begin----------------------------------------------------
ProcedureCDLL.l Add(a.l, b.l)
ProcedureReturn a + b
EndProcedure
; End------------------------------------------------------
After the build of the DLL I create a VBS program to check the functionality:
'-Begin----------------------------------------------------
Set DX = CreateObject("DynamicWrapperX")
DX.Register "DLL_Tutorial.dll", "Add", "i=ll", "r=l"
res = DX.Add(2, 😎
MsgBox res '10
'-End------------------------------------------------------
Up to this point all works correct, the message box shows 10.
Now I take your ABAP program and my library and runs it in my environment and all works as expected.
Generally it works.... Your ABAP code is perfect.
What could be your problem?
Are you working with a 64-bit Windows environment? If so, register dynwrapx.dll from syswow64 directory and not from system32.
That is the only reason I can see for the moment.
Hint: It is not necessary to register the dynwrapx library with the TAC SOLE.
Let us know your results.
Cheers
Stefan
- SAP Managed Tags:
Hi Stefan
Thanks for your reply.
It's a good idea to test dll firstly via VBS 🙂
Yes, my testing OS is 64bit based. I copied the file dynwrapx to folder syswow64 and run regsvr32 dynwrapx.dll, is that right?
But seems the testing VBS does not work
Best regards
James
- SAP Managed Tags:
Hello James,
you are registering the library correct.
But you call the VBScript via the Explorer, so it starts the 64-bit WSH. Call the script via the command line in the directory syswow64.
With this way you start the 32-bit WSH and now it should work.
Let us know your results.
Cheers
Stefan
- SAP Managed Tags:
