Failed to import the ActiveX Control

SUGGESTED

Having problem with my SAGE 2020 (300 Premium) (Build 0)

When I tried to add COM Components for example AP2100 (AccpacAP2100.AccpacAP2100UICtrl)

and drag that to my Empty Project .NET (VB), it show's the error below (Failed to import the ActiveX Control). I already tried visual studio 2012 up-to 2019. But still the same.

VB6 is working fine, but I don't want to use that and never go back with it.

Let me know what should I need to do? I saw this thread (https://www.sagecity.com/support_communities/sage300_erp/f/sage-300-reports-macros-and-customizations/79169/sage-300-version-2014) but I cannot see the thing called "ObjSafe.tlb" on my machine.

Parents
  • 0

    Hey, We've recently resolved this issue or at least have an immediate solution as we address a long term solution. It seems that the ObjSafe.tlb file is being removed during the installation, likely by an anti-virus program. Since the VB UIs are built with the lObjectSafety implementation, when this file is missing, the axInterop utility complains.

    Short Term Solution: Here is a link (www.dropbox.com/.../ObjSafe.zip) to a zip file containing the ObjSafe.tlb file. Unzip into your Sage Runtime folder and the issue is resolved and you can now add the OCX to the Visual Studio Toolbox and then drop it on your WinForms screen (C# or VB.Net).

    Long Term Solution: We may decide to remove the lObjectSafety implementation in the VB UIs (single implement statement) since the VB OCXs are no longer supported being run in Internet Explorer.

Reply
  • 0

    Hey, We've recently resolved this issue or at least have an immediate solution as we address a long term solution. It seems that the ObjSafe.tlb file is being removed during the installation, likely by an anti-virus program. Since the VB UIs are built with the lObjectSafety implementation, when this file is missing, the axInterop utility complains.

    Short Term Solution: Here is a link (www.dropbox.com/.../ObjSafe.zip) to a zip file containing the ObjSafe.tlb file. Unzip into your Sage Runtime folder and the issue is resolved and you can now add the OCX to the Visual Studio Toolbox and then drop it on your WinForms screen (C# or VB.Net).

    Long Term Solution: We may decide to remove the lObjectSafety implementation in the VB UIs (single implement statement) since the VB OCXs are no longer supported being run in Internet Explorer.

Children
No Data