MonoReport with OpenOffice.org 3

[San]

I am trying Monoreport from a VB.net winforms application using
OpenOffice.org 3.
Calling TemplateProcessor.Process(ODSTemplate, ODSFile, ReportDS)
produce an error :
"Could not load file or assembly 'cli_types ..."

At http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/CLI/CLI_Language_Binding
they state that "cli_types.dll is replaced by cli_oootypes.dll" ...
and "The consequence of this is that all client programs which linked
with cli_types.dll do not work anymore."

Will MonoReport be updated soon or is there any other way to get past
this error without installing an older OpenOffice version?

[MonoReport Team]

MonoReport have been tested with both OpenOffice.org versions 2 and 3,
but version that available to download from MonoReport.com is linked
to OpenOffice.org 2.

We will update installation package on MonoReport.com soon to support
OpenOffice.org version 3.

Thank you,
MonoReport Team

On Jan 13, 5:56 pm, San <sanniepomp...@gmail.com> wrote:
> I am trying Monoreport from a VB.net winforms application using
> OpenOffice.org 3.
> Calling TemplateProcessor.Process(ODSTemplate, ODSFile, ReportDS)
> produce an error :
> "Could not load file or assembly 'cli_types ..."
>

> Athttp://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUN...

[MonoReport Team]

New version of MonoReport installation package (linked with
OpenOffice.org version 3 libraries) available to download at
http://www.monoreport.com/.

MonoReport Team

On Jan 13, 5:56 pm, San <sanniepomp...@gmail.com> wrote:

> I am trying Monoreport from a VB.net winforms application using
> OpenOffice.org 3.
> Calling TemplateProcessor.Process(ODSTemplate, ODSFile, ReportDS)
> produce an error :
> "Could not load file or assembly 'cli_types ..."
>

> Athttp://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUN...

[San]

I appreciate the quick response from the MonoReport Team.

Thank you,
San

On Jan 13, 6:18 pm, MonoReport Team <w...@4g-soft.com> wrote:
> New version of MonoReport installation package (linked with

> OpenOffice.org version 3 libraries) available to download athttp://www.monoreport.com/.

[San]

Using the latest MonoReport with OpenOffice.org 3 in a VB.NET winforms
application I get an ErrorCodeIOException when Calling
TemplateProcessor.Process.
The process runs for a while and copies the template to the report
location but OpenOffice apparently fails during the final output of
the report with the following stacktrace information;

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage
(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke
(MessageData& msgData, Int32 type)
at unoidl.com.sun.star.frame.XStorable.store()
at
#=q7z3YhnBsBLvnWAPfWd0oKh3lkfLxg7NA54B4EeA9wMgrPqpzmp0ZReEd8a5govTgY8w4uDwt8kTUpj2lorgAJw==.Process
()
at
#=qXrD1g9KcQkA4U3ltKglaX6Sxx3e2pPNaf3eKYOQUG9ywh_phgSRj8l_nMCcsN1XIdgNH1i3LXA2Wf73Pwa44rg==.#=qV
$FPeoB$YXcCUT17gB2iOg==(ProcessingOptions #=qWylSekjun9yFlV9fVw_4aA==)
at FogSoft.MonoReport.Processing.TemplateProcessor.Process
(ProcessingOptions options)

I will gladly supply any additional information if required.

Please advise,
San

[MonoReport Team]

San, some additional information will be helpful to solve this issue:

- what is the value of ErrorCodeIOException.ErrCode that you getting?
- what is the value of OutputFileName used in ProcessingOptions?

MonoReport Team

[San]

- ErrorCodeIOException.ErrCode = 796
- OutputFileName = "\\San\My Appdata\Test Data\ReviewedSR.ods"
I tested the OutputFileName without the network path (C:\Test Data
\OOoTemplates\ReviewedSR.ots) and get the same error.
The template is copied without alteration to this location when
TemplateProcessor.Process starts but then the error.

At first I tried without setting the default for TemplateProcessor
then I changed to the following code with the same result;

Imports System.IO
Imports FogSoft.MonoReport.Processing
---
Dim ODSTemplate as string = "\\San\My Appdata\OOoTemplates
\ReviewedSR.ods" 'Also tried as .ots
Dim ODSFile as string = "\\San\My Appdata\Test Data\ReviewedSR.ods"
If FileExist(ODSFile) Then
FileDelete(ODSFile)
End If
Dim MonoType As New FogSoft.MonoReport.Processing.ProcessingOptions
(ODSTemplate, ODSFile, ReportDS)
MonoType.TemplateProcessor = TemplateProcessorType.OpenOfficeCalc
TemplateProcessor.Process(MonoType)

I suspect the problem lies with the passing of filetype arguments in
the ParamArray to the OOo InvokeMember method under VB.NET. Apparently
C# does this differently?

I hope this helps.

San

[MonoReport Team]

According to OpenOffice error codes 796 is ERRCODE_IO_NOTEXISTSPATH

Please verify that path specified for OutputFileName is exist or first
try to set OutputFileName to some simple path, without network paths
or space characters, for example OutputFileName = "c:\Generated.ods"

MonoReport Team

[San]

Great. I tried that already as stated in my previous post and get the
same error.
But acting on your tip I took a chance and ...
By keeping my full network path and changing the extension (only) of
my OutputFileName to .pdf does produce a proper .pdf document at the
expected location without Errorcode 796.
A PDF output is actually what I need although I did not find this
behaviour in the MonoReport documentation.

Thanks again to the MonoReport Team,
San

[MonoReport Team]

A generation of .pdf reports is not documented feature of MonoReport
yet (by the way, this works only with OpenOffice as report generator).

So you still having problems generating *.ods outputs, even with
simple local paths as, for example, "c:\test.ods" ?

Thank you,
MonoReport Team

[San]

Yes. Even with templateFilename = "C:\Monorep.ods" and outputFilename
= "C:\test.ods".
C:\test.ods is created before the error occur but not updated.
Outputting as .pdf works fine although it prints free version
information at the bottom right footer.

Hope I could be of more help.

Thank you,
San

[MonoReport Team]

San, to resolve this issue we need more additional information:
- full version of OpenOffice that you using,
- version of operating system,
- can you send us a sample of report template that causing this issue?

We will try to reproduce this issue in similar environment and fix it.

PS. Information about MonoReport is always present in footer of
generated reports in free version, it is a normal behaviour.

Thank you,
MonoReport Team

[San]

OpenOffice version 3.1.1 (Build:9420)
Windows XP (Service Pack 3)
Visual Studio 2008 (Version 9.0.30729.1 SP)
.NET Framework (Version 3.5 SP1)

I would gladly send you a sample of the Template file, especially
because I cannot get PB (Page Break) to work in before the change of
group in a grouped report, but I find no option to add attachments to
this post.

San

[MonoReport Team]

San, please submit your report template on this page
http://groups.google.com/group/monoreport/files

Thank you,
MonoReport Team

[San]

Done.
I would like to start t1,l0 {Town} each on new page but get no effect
with PB marker on previous row. Maybe I do it wrong?

Thanks,
San

On Jan 15, 5:20 pm, MonoReport Team <w...@4g-soft.com> wrote:
> San, please submit your report template on this pagehttp://groups.google.com/group/monoreport/files

[MonoReport Team]

San, we have found the cause of ErrorCodeIOException with ErrCode =
796 (ERRCODE_IO_NOTEXISTSPATH) during processing of OpenOffice.org
templates. This exception occurred because of using of OpenOffice.org
template files (*.ots) instead of document files (*.ods) as MonoReport
templates. We will fix this issue in future versions of MonoReport. To
bypass this issue you should save your report template as
OpenOffice.org document (*.ods) and change reference to this file in
your application.

Regarding using of Page Breaks in report templates: because of nature
of MonoReport templates processing we are not using original Page
Breaks from report templates. Instead of we are using special marker
PB (or PageBreak in full notation) to add page breaks to final report.
Unfortunately this feature is implemented only for cases when using
Microsoft Excel as processor of reports. Implementation of custom page
breaks for OpenOffice.org is a planned feature.

Thank you,
MonoReport Team