Unfortunately, there seems to be an incompatibility issue in the OCX files with respect to .NET. The reason I have seen so far is, that the OCX DLL-Interface is not clean and is hence rejected by .NET. This immediately leads to the solution, that you already described. Put a wrapper around the OCX and then you can use it from .NET. Whether C# or VB does not make a big difference.
Dig Deeper on SAP ABAP
Related Q&A from Axel Angeli
An SAP user wants to know how to upload data into SAP R/3 when SAP Scripting is not enabled. Continue Reading
An SAP user is receiving an error message while integrating SAP iDoc PORDCR1 for a purchase order. Continue Reading
An SAP user is having difficulty with PERNR iDoc while transporting data from SAP to an external system. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.