Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Cannot Register type library for qlikocx 10

Hi,

i have an error, when i try to register the type library for qlikview ocx 10.

There isn't errors when i try with the version 9.

Has anyone try to register qlik ocx 10?

8 Replies
Not applicable
Author

Hi,


I can register it, I can add a document to my application but I can't access the properties as I get error:

Error 1 Reference required to assembly 'QlikView, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' containing the type 'QlikView.Doc'. Add one to your project. ....

Not sure how I can get around this.

You have an idea?

Not applicable
Author

Hi,

I finaly succedeed.
Run regsvr32 for QlikOcx.ocx and qvp.dll, then use Aximp.exe in C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\ with the Qlikocx.ocx .

I can now access the propoerties of the documents.

Cheers

Thanks to QV for the info btw.

Not applicable
Author

The solution of running Aximp.exe on the OCX file to generate the assembly DLLs and then add those to the project seemed to work for me as well.   Not sure why I had to do that or why that information is not in the OCX reference manual, but it looks like I'm on my way now...

marksouzacosta
Partner - Specialist
Partner - Specialist

All right people, that's how I got around this OCX problem.

    In the "QlikViewOCX reference manual.pdf" they have several ways on how to add the component to your project. VB6, C++ and Delphi are pretty much covered there, but the .NET side of it was still a bit clouded.

    I saw in there that they comment something about QvX64OCX.exe (which is nowhere to be found, according to Google).

    Since my box is x64, and most of my clients are too, I had to focus on that architecture.

    Basically, I logged into Qlikview.com with my partner login and downloaded "QvOCXSetupRedist.exe" (version 9.0 SR7, which is the most up-to-date version by the time of this reply). It created the "C:\Program Files (x86)\QlikView\QlikOCXx64" and C:\Program Files (x86)\QlikView\QlikOCX" folders, which I thought would bring light to my problemas.

    However, I kept failing to import the OCX into my projects. Everytime, a different COM message.

    So, I finally bumped on this AxImp.exe reply on this thread (which stands for ActiceX Import - I suppose), and created 3 new DLL's based on the x64 QlikOCX.ocx component. Referencing all three new component allowed me to start creating Qlikview objects and performing all the tasks I had to.

    I hope that can be of use to you guys. If you still have trouble creating projects with QlikOCX component, please let me know and I'll see what I can do.

    Cheers to all

Read more at Data Voyagers - datavoyagers.net
Not applicable
Author

Hi,

I have made the  dll classes using AxImp in the visual studios command prompt. I have referenced the classes in my project. at the moment I am trying to open a qlikview Application using the GetObject method but it doesn't work and I have tried openDoc too it doesn't work. Visual studios complains it is unable to load QlikOcx.ocx. I have registered QlikOcx.ocx, have made the rapper classes and pointed the rapper classes - surely visual studios should regonise QlikView Object method calls. I don't know what the problem is.

Not applicable
Author

Hello,

I reccently changed my project from 3.5 to 4.0 NET and since I get following error:

Could not load file or assembly 'QlikOCXLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

I'm using C# VSTO 2010

I imported the QlikOCXLib.dll created 9/11/2012.

It did work well before on 3.5 NET now that my project changed to 4.0 NET it doesn't recognizes the assembly.

Even when I try to put a new reference for it.

Any idea?

flipside
Partner - Specialist II
Partner - Specialist II

AFAIK it doesn't work with .net4.0, you'll need to rollback to 3.5.

flipside

Not applicable
Author

Thanks.

That was what I thought, but didn't notice, because I had some other errors, then decided to switch to 4.0 and while reopening it was stuck.

Thanks for confirmation.