ActiveX examples from NI not working

[MarknTX]

Upgraded to Labview 7 and now the activex items for excel no longer work. Specific example is the excel easy text.vi. It is not executable because of various property nodes are not valid. It worked great under 6.1. Any ideas?

[LucaP.]

Hello Markn TX,

Try to update the RGT 1.0.x for LV 7:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/71e2b0213cedd6b686256d4a0059a590?OpenDocument

Hope this helps

Luca

[MarknTX]

I installed this and it did not fix the problem. I am desperate for this to work, but if I dont fix it soon, I am going to go back to excel DDE commands which work perfect.

[LucaP.]

Is it not working with both (LV 6.1 and LV7)?

The way to go is normally:
1. Install the Report generation toolkit 1.0.1 (select the correct MS office version).
2. If you're using LV 7 then run the update I've already mentioned before.
3. If you want to use the toolkit with LV 6.1 and LV 7 then review the KB linked below:
http://digital.ni.com/public.nsf/websearch/41E5E2A0E94158E086256B8100535560?OpenDocument

Regards,
Luca

[MarknTX]

I got ahold of tech support and it was registry entries on my computer. Updated the older version keys and all works great. Thanks for everything. Mark

[Wiebe@CARYA]

Hi,

It seems like this could be a solution to a excel report problem we have.
Could you tell us the exact changes you've made?

Thanks,

Wiebe.

"MarknTX" wrote in message
news:5065000000050000007A360100-1066448259000@exchange.ni.com...
> I got ahold of tech support and it was registry entries on my
> computer. Updated the older version keys and all works great. Thanks
> for everything. Mark

[MarknTX]

Send me your email at madams@airmail.net and I will tell you. I will have to search the registry and find it again. You might be able to call NI and tell them to search their knowledge base for registry entries required for the report toolkit. That is how my app engineer found it. They are VERY helpful.

[Wiebe@CARYA]

Hi,

I've received a set of registry changes once. It did not solve the problem.
There seems to be some inconsistency with Excel ActiveX, if the default
language is different from the OS language. This problem is not LabVIEW
specific, but it would be nice to have it fixed.... It could also have
something to do with 'early binding', but in LV there's no control over
this.

Thanks anyway,

Wiebe.


"MarknTX" wrote in message
news:50650000000500000017370100-1066448259000@exchange.ni.com...
> Send me your email at madams@airmail.net and I will tell you. I will
> have to search the registry and find it again. You might be able to
> call NI and tell them to search their knowledge base for registry
> e
ntries required for the report toolkit. That is how my app engineer
> found it. They are VERY helpful.