What is the difference between OCX, WorkBench and Webparts ? Having OCX license, does it mean WorkBench and Web parts works with this ? Can someone help ?

[anil_y_86]

What is the difference between OCX, WorkBench and Webparts ?  Having OCX license, does it mean WorkBench and Web parts works with this ?  Can someone explain ?

[#2]

OCX = Microsoft Office integration. Named User/Document CAL and QlikView Server required. No special license needed.

Webparts = to integrate QlikView with Microsodt SharePoint, i.e. display individual QlikView objects on a SharePoint page (superseded by Workbench license)

Workbench = Visual Studio .NET add-on and license to allow integration/mash-ups

[Peter_Cammaert]

That's not the whole story.

OCX is the QlikView core packaged as a component that can be integrated in other (.NET) proprietary applications, after which the two can be dropped off at customers who haven't the faintest idea what QlikView or a CAL are.

For that situation you'll need an OCX license embedded in the proprietary application, a license that Anil clearly already owns.

Peter

[#4]

You're right Peter. Anil must be a QlikView OEM Partner (or customer using a QV OEM solution) as it is a specialised license only available to OEMs. Officially called the "OEM - QlikView OCX Local Client" license.

In my non-OEM experience OCX has been mainly used to integrate dynamic QV charts into PowerPoint presentations. No special license is required for that above and beyond the standard QlikView Server license and user CAL.

[anil_y_86]

Thank you Peter and Kai for your explanation and this forum is really helping me alot.

Regs,

Anil