LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

excel report generation error

Hi,

Does anyone have experienced (and solved) this behaviour?

I've been using the report generation toolkit to build word report without
problem. I've also solved a lot of problems in the excel part of the toolkit
(e.g. building graphs with >20000 points). It finally works in development
environment.

Now when I install the executable (, with the installer) the word reports
still work, but the excel report don't. The executable does run on a
different system, but the excel versions are the same (both Excel 2000).

I have copied the excel library in the data directory of the executable.

The following error is generated:

-2147319784
Old format or invalid type library
Excel_Open.vi

This is the first report generation vi that is called. I us
e it to open a
template.

Any help is appreciated.

Wiebe.
0 Kudos
Message 1 of 9
(4,331 Views)
Hi,

Surfing the internet, I found this comment:

*Start quote*
Sometimes you'll find that a parameter is required that isn't mentioned
anywhere in the application's documentation. This happens when you need to
specify system information: the chief example of this is the lcid, which is
a locale identifier, and which pops up all over the place in Excel. The good
news is that there is a constant in the Windows unit which provides you with
the correct value, LOCALE_USER_DEFAULT:

var
lcid: integer;
begin
...
lcid := LOCALE_USER_DEFAULT;
Excel.Visible[lcid] := True;

There's also a function, GetUserDefaultLCID, but using that value can cause
an error, complaining about an 'old format or invalid type library' on some
setups. Using LOCALE_USER_DEFAULT for the
LCID value should fix that.

*End quote*

Could this be the problem?

Regards,

Wiebe.



"Wiebe@AIR" wrote in message
news:3e79a3aa$0$140$e4fe514c@dreader9.news.xs4all.nl...
> Hi,
>
> Does anyone have experienced (and solved) this behaviour?
>
> I've been using the report generation toolkit to build word report without
> problem. I've also solved a lot of problems in the excel part of the
toolkit
> (e.g. building graphs with >20000 points). It finally works in development
> environment.
>
> Now when I install the executable (, with the installer) the word reports
> still work, but the excel report don't. The executable does run on a
> different system, but the excel versions are the same (both Excel 2000).
>
> I have copied the excel library in the data directory of the executable.
>
> The following error is generated:
>
> -2147319784
> Old format or invalid type library
> Excel_Open.vi
>
> This is the first report generation vi that is called. I use it to open a
> temp
late.
>
> Any help is appreciated.
>
> Wiebe.
>
>
0 Kudos
Message 2 of 9
(4,331 Views)
Hi Wiebe,
I recently had the same problem: could not run an executable using report generation toolkit version 1.0.1. Note that I developed several applications that used version 1.0 without any problem.
I found out that the problem is caused by the sub-vis:
Excel Find Application Directory.vi
Word Find Application Directory.vi
They are called by the New Report.vi, their function is to locate _exclsub.llb and _wordsub.llb depending if the report is generated by the developed system or by an application (.exe).
The point is that these vis of the version 1.0.1 do work as supposed to: they can not locate the support libraries in the data subfolder of an application; just take a look at their diagrams and you'll understand why!
Fortunately I had on anot
her pc installed the version 1.0 and I saw that the same vis were completely different, and working...
I simply copied the old ones over the new in the NIReport.llb and everything works fine!
I attach here the vis, please let me know if it solves your problem. If it does we should report it to NI.

Good luck,
Alberto
Download All
0 Kudos
Message 3 of 9
(4,331 Views)
Hi,
I have encountered the same problem on my system after the upgrade to LabView 6.1. I was not able to run any of the examples delivered with LabView.
As I remember me, NI-Support recommands to recompile (menu Tools/Advanced/Mass compile...) the Report library "C:\Program Files\National Instruments\Labview 6.1\vi.lib\Utility\NIReport.llb". Ths has to be done each time you upgrade or reinstall LabView 6.1
Since the recompilation of the library, all my reports are working perfectly.
I hope this will help you too.
0 Kudos
Message 4 of 9
(4,331 Views)
Hi,

Thanks for the reply.

I'll deffinatelly try it, but I didn't upgrade to any new version since I
installed the report generation toolkit. Perhaps the vi's are delivered in
an older version.

In your case, did it not work at all, or only after compiling (building
..exe)?

I'll let you know the results.

Regards,

Wiebe.


"phidu" wrote in message
news:50650000000500000038DF0000-1042324653000@exchange.ni.com...
> Hi,
> I have encountered the same problem on my system after the upgrade to
> LabView 6.1. I was not able to run any of the examples delivered with
> LabView.
> As I remember me, NI-Support recommands to recompile (menu
> Tools/Advanced/Mass compile...) the Report library "C:\Program
> Files\National Instruments\Labview
6.1\vi.lib\Utility\NIReport.llb".
> Ths has to be done each time you upgrade or reinstall LabView 6.1
> Since the recompilation of the library, all my reports are working
> perfectly.
> I hope this will help you too.
0 Kudos
Message 5 of 9
(4,331 Views)
Hi again Wiebe,
have you checked on your machine the 2 vis I mentioned in my previous post?
I'm really curious because I actually had that problem and it was solved by replacing the vis.
Thanks in advance,
Alberto
0 Kudos
Message 6 of 9
(4,331 Views)
Alberto,

Thank you for checking, I did not see any messages from you. So I'll check
the on line newsgroup at NI.

Outlook seems to leave out messages, and it seems the prefere the important
messages.

I'll get back on it.

Thanks,

Wiebe.


"alberto" wrote in message
news:50650000000500000067DF0000-1042324653000@exchange.ni.com...
> Hi again Wiebe,
> have you checked on your machine the 2 vis I mentioned in my previous
> post?
> I'm really curious because I actually had that problem and it was
> solved by replacing the vis.
> Thanks in advance,
> Alberto
0 Kudos
Message 7 of 9
(4,331 Views)
Alberto,

The attachments where blocking the message...

The files that are used on my system are the new ones. Also, if the name is
incorrect, LV reports an error "Open VI Reference in New Report.vi".

Thanks anyway,

Wiebe.



"Wiebe@AIR" wrote in message
news:3e82bfa4$0$142$e4fe514c@dreader5.news.xs4all.nl...
> Alberto,
>
> Thank you for checking, I did not see any messages from you. So I'll check
> the on line newsgroup at NI.
>
> Outlook seems to leave out messages, and it seems the prefere the
important
> messages.
>
> I'll get back on it.
>
> Thanks,
>
> Wiebe.
>
>
> "alberto" wrote in message
> news:50650000000500000067DF0000-1042324653000@exchange.ni.com...
> > Hi again Wiebe,
> >
have you checked on your machine the 2 vis I mentioned in my previous
> > post?
> > I'm really curious because I actually had that problem and it was
> > solved by replacing the vis.
> > Thanks in advance,
> > Alberto
>
>
0 Kudos
Message 8 of 9
(4,331 Views)
Well, for everyone that is interrested, here's a way to solve it...

NI send me some information about changing the registry. It looked like it
should fix the problem, but it didn't in my case.

After 3 weeks of blood, sweat and tears a colleage noticed I should try it
on LV 6.1. (First I had to find a local machine that showed the same
behaviour.) And it did work on 6.1! Building an executable did not have
anything to do with it, the development environment showed the same problem.

So this not a fix of the problem. On the internet some sources say that this
is a known problem when a 16 bit server opens a 32 bit client, or visa
versa, and early binding is used. Perhaps the way LV opens an automation
reference is changed between 6.0.2 and 6.1? Who knows...

Rega
rds,

Wiebe.



"Wiebe@AIR" wrote in message
news:3e79a3aa$0$140$e4fe514c@dreader9.news.xs4all.nl...
> Hi,
>
> Does anyone have experienced (and solved) this behaviour?
>
> I've been using the report generation toolkit to build word report without
> problem. I've also solved a lot of problems in the excel part of the
toolkit
> (e.g. building graphs with >20000 points). It finally works in development
> environment.
>
> Now when I install the executable (, with the installer) the word reports
> still work, but the excel report don't. The executable does run on a
> different system, but the excel versions are the same (both Excel 2000).
>
> I have copied the excel library in the data directory of the executable.
>
> The following error is generated:
>
> -2147319784
> Old format or invalid type library
> Excel_Open.vi
>
> This is the first report generation vi that is called. I use it to open a
> template.
>
> Any help is appreciated.
>
> Wiebe.
>
>
0 Kudos
Message 9 of 9
(4,330 Views)