x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 120 subscribers
  • Views 4473 views
  • Users 0 members are here
Browse Forums
Announcements
270
topics
260
replies
Databases and Operating Systems
763
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
852
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
877
topics
3k
replies
Sage CRM for Sage 300
183
topics
414
replies
BryanG

Failed to import the ActiveX Control

SUGGESTED
Posted By

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

    I've just tried it on a dev machine with no issues. Running VS 2019 v16.7.6, with Sage 300 2020 PU2.

    I created a new c# .NET win forms app. Changed the target type to x86. Created a new form. In the toolbox I added the AP2100 control and dragged it in. It automatically referenced accpacCOMAPI, the datasource, etc. All that can be seen from the screen shot below. No issues.

    I have a few projects on Sage300 2019 using WPF with sage finder controls working all ok.

    Can i suggest that you check the target type is x68 and clear your obj and bin folders - then clear your solution.

    The only issues I've encountered is when upgrading projects to later versions of Sage300. I basically have to remove all references that are auto-created, clear the solution (and delete the the obj and bin folders), then add the updated controls to the toolbox and drag them into a dummy form. It automatically add all new references and updates the existing controls.

Reply
  • 0

    I've just tried it on a dev machine with no issues. Running VS 2019 v16.7.6, with Sage 300 2020 PU2.

    I created a new c# .NET win forms app. Changed the target type to x86. Created a new form. In the toolbox I added the AP2100 control and dragged it in. It automatically referenced accpacCOMAPI, the datasource, etc. All that can be seen from the screen shot below. No issues.

    I have a few projects on Sage300 2019 using WPF with sage finder controls working all ok.

    Can i suggest that you check the target type is x68 and clear your obj and bin folders - then clear your solution.

    The only issues I've encountered is when upgrading projects to later versions of Sage300. I basically have to remove all references that are auto-created, clear the solution (and delete the the obj and bin folders), then add the updated controls to the toolbox and drag them into a dummy form. It automatically add all new references and updates the existing controls.

Children

*Community Hub is the new name for Sage City