Necessary module for distribute application with excel report

[568]

Hi,

I am trying to installing the cvi project (my developed project on cvi) after creating a distribution on new PC that no have a cvi compiler. My project use excel2000 driver supplied by NI. 

After i installed project on new PC, i receive the message that the driver does not see the excel on this PC. 

Note: Excel exist on this PC, and working properly when i start him manually.

After this fail, I trying to create the distribution from excell2000dem project that supplied by cvi, and i receive a same problem.

What i need to do when i create the distribution?

Thank you 

Very Much

[RobertoBozzolo]

No special libraries should be needed to run a CVI app which interacts with Excel. The problem may lie in the Excel instance installed in the machine, which may lack the interface with other programs: which is the version installed? And which exact error do you receive in your app?

[568]

Hi Roberto, Thank you for your reply.

I use Excel 2016 on my develop station and I use CVI 2019, and the target station have a Excel 2019, full office version.

I take NI example and trying to run. Please see attached file that shows the error.

How can I solve this problem?

Thank you

Boris

[rolfk]

What about the bitness of the involved applications? CVI, Excel?

[568]

Hi, 

I am very sorry, but I don't understand what you mean when you say "bitness"? What is it?

Thank you

Boris

[rolfk]

Your Windows 10 is almost certainly 64-bit and your Office 2019 too. Your LabWindows CVI prgram however is likely set to generate 32-bit applications. While ActiveX would allow for 32-bit applications to call 64-bit components and vice versa that is usually not supported by most ActiveX components and while it can be made to work with registry hacking it always has potential trouble to render other working connections invalid so shouldn’t be done if at sll possible.

[RobertoBozzolo]

While this can be true, it is to be said that I never had problems running 32-bit CVI applications with Excel Interface even on 64-bit systems.

I wonder if 568 has tried to do what the error message suggests: open Excel and try connecting to an open instance instead of opening a new one.