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.
>
>