Attention Pragnaan !!

rbuser

Hi,

I have a export problem to Excel. Some columns or fields are not export to excel. (RTF, PDF exports successfull)
I am send 2 times mail to Pragnaan with example files and problem descriptions. (RAF, XLS and preview screen capture files).

But i don't get any notify mail from pragnaan..

This problem very important for me. Because our customers will be crazy !!!!

Best regards,

Ismet Celebi

rbuser

Hi,

I ran into the same problem and can help a little. The problem is that when
Pragnaan exports they assume a fixed row height and a fixed column width.
So they make a grid and then they print to that grid. If two lines happen
to
fall in the same row, it puts both items in the same cell and so the first
gets
overwritten and wiped out. Same thing with columns.

The problem is made worse by the fact that they don't recalculate the cell
size based on the font size so you will find that if you change fonts, which
lines are lost will change.

To try and address this you can set the PositionalGrid Dimension to
something smaller. The height starts as 4234 and we made it 3000. This
is the size of the cell by making it smaller you reduce the chance that two
lines are going to overlap in the same cell. You also then set the line
spacing to lsNoBlank to eliminate the blank lines that reducing the Height
causes. These items are both found in the Excel section of the
PSRBExportMasterControl component.

I think what they should do is never allow an overlap. If the cell already
had data, create a new row (or column) and shift everything below it
down (or to the right).

I hope that helps some.

Thanks,
Joseph Gordon

rbuser

Hi Joseph,
Thats ok. Very thanks.

But why not reply my email?

Ismet Celebi


"Joseph Gordon" wrote in message news:416c3ff7$1@dm500....
Hi,

I ran into the same problem and can help a little. The problem is that when
Pragnaan exports they assume a fixed row height and a fixed column width.
So they make a grid and then they print to that grid. If two lines happen
to
fall in the same row, it puts both items in the same cell and so the first
gets
overwritten and wiped out. Same thing with columns.

The problem is made worse by the fact that they don't recalculate the cell
size based on the font size so you will find that if you change fonts, which
lines are lost will change.

To try and address this you can set the PositionalGrid Dimension to
something smaller. The height starts as 4234 and we made it 3000. This
is the size of the cell by making it smaller you reduce the chance that two
lines are going to overlap in the same cell. You also then set the line
spacing to lsNoBlank to eliminate the blank lines that reducing the Height
causes. These items are both found in the Excel section of the
PSRBExportMasterControl component.

I think what they should do is never allow an overlap. If the cell already
had data, create a new row (or column) and shift everything below it
down (or to the right).

I hope that helps some.

Thanks,
Joseph Gordon

rbuser

Hi Joseph,

I try set PositionalGrid Dimension.height = 3000.
One report is ok but other some reports are not okey. Now some columns are not export to excel....

How can i do?

Thanks,

Ismet Celebi


"Joseph Gordon" wrote in message news:416c3ff7$1@dm500....
Hi,

I ran into the same problem and can help a little. The problem is that when
Pragnaan exports they assume a fixed row height and a fixed column width.
So they make a grid and then they print to that grid. If two lines happen
to
fall in the same row, it puts both items in the same cell and so the first
gets
overwritten and wiped out. Same thing with columns.

The problem is made worse by the fact that they don't recalculate the cell
size based on the font size so you will find that if you change fonts, which
lines are lost will change.

To try and address this you can set the PositionalGrid Dimension to
something smaller. The height starts as 4234 and we made it 3000. This
is the size of the cell by making it smaller you reduce the chance that two
lines are going to overlap in the same cell. You also then set the line
spacing to lsNoBlank to eliminate the blank lines that reducing the Height
causes. These items are both found in the Excel section of the
PSRBExportMasterControl component.

I think what they should do is never allow an overlap. If the cell already
had data, create a new row (or column) and shift everything below it
down (or to the right).

I hope that helps some.

Thanks,
Joseph Gordon

rbuser

Hi,

I have no idea why they would not be responding to emails.
They we pretty good at responding about 6 months ago
when I was first researching this. Since they are in India
I would e-mail before the end of the day and get a response
the next morning. I know that were making a new product.
It's possible that there focus has shifted.

You can try changing the PositionalGridDimension.Width
down from 16000 and set the column spacing to see if that
helps

The real crux of the problem is that exporting a report to
a file format is not the same as exporting data to a file
format. In exporting a report to excel they (Pragnaan) is
trying to get excel to look like that page. What you (and I)
want is the information on the page. The positioning on
the page is secondary.

I don't know if the Waler ExtraDevice exports do it better,
but you might look there too.

Thanks,
Joseph Gordon

rbuser

Hi Joseph Gordon,

Are you working in Pragnaan?

Thanks,
Ismet Celebi


"Joseph Gordon" wrote in message news:416d5d4b$1@dm500....
Hi,

I have no idea why they would not be responding to emails.
They we pretty good at responding about 6 months ago
when I was first researching this. Since they are in India
I would e-mail before the end of the day and get a response
the next morning. I know that were making a new product.
It's possible that there focus has shifted.

You can try changing the PositionalGridDimension.Width
down from 16000 and set the column spacing to see if that
helps

The real crux of the problem is that exporting a report to
a file format is not the same as exporting data to a file
format. In exporting a report to excel they (Pragnaan) is
trying to get excel to look like that page. What you (and I)
want is the information on the page. The positioning on
the page is secondary.

I don't know if the Waler ExtraDevice exports do it better,
but you might look there too.

Thanks,
Joseph Gordon

rbuser

Hi,

I started with ExtraDevices but I also use WPTool for the rich text
stuff. Pragnaan came along and had that capability first. So, I
switched to it. When ExtraDevices got that capability too I tried
to switch back to it but it was taking 30 seconds to generate a
pdf page which took just a few seconds on Pragnaan (That might
have been a bug in ExtraDevices). I also liked better the ability
to bring up a setup dialog in Pragnaan and the ability to open the
file once it is created. So, I use it but am not locked into it.

Thanks,
Joseph Gordon

rbuser

Hi,

While you are looking for solutions to export your RB reports, you would NOT
want to ignore eDocEngine. eDocEngine provides unmatched flexibility and support
for exporting reports. eDocEngine supports high quality Excel rendering, high
quality rendering of richtext (including WPRichText) to PDF and other formats
and much more.

Here's a complete EXE demo of the new version releasing soon: (save your report
as .raf, load and export in this EXE demo):
http://www.gnostice.com/download/v200p/edocpdfv2_demo.zip

For just the RB Export EXE demo please use this link:
http://www.gnostice.com/edocengine/download/ext/edoc_rb_demo.zip

For a full feature trial version, please log on to:
http://www.gnostice.com/


Why eDocEngine is the preferred solution for exporting reports?
===============================================================
* Supports exporting to over 20 popular formats, including PDF, RTF, HTML,
Excel, TIFF, SVG, PNG, JPEG, Metafile and many more.

* Integrates tightly with your reporting tool to enable CODE-FREE
configuration and execution at design-time as well as run-time.

* Allows for extensive configuration of exports through vast set of
intuitively named and grouped properties.

* Charts and Metafiles are rendered as vector graphics to ensure sharp,
scalable graphics in the generated PDF, RTF and other supported formats.
Vector graphics also ensures files are extremely compact and easy to
distribute.

* Supports RichText rendering as RichText (not image) in all document
formats ensuring crisp documents that can be text searched and enlarged
without loss of quality.

* PDF engine supports full set of advanced features including, compression,
encryption, TrueType fonts, font embedding, font sub-setting,
international characters (European, Chinese, Japanese...), bookmarks,
notes annotations and more.

* All standard and custom controls are exported, WITHOUT the need for
extra coding on your part.

* Excel and all spreadsheet engines support intelligent cell formatting
enabling values to be encoded in the correct format, automatically.

* Supports End-User configuration of exports through *customizable*
run-time dialogs.

* All engines of eDocEngine are highly optimized for HIGH-SPEED export
of reports.

* Highly flexible architecture enables custom programmatic exporting. For
example, you can combine multiple reports then insert your own custom
page (using the eDocEngine API), then append a few more reports and
make a single output document of them.

* And much, much more...

--
Girish Patil
Gnostice Information Technologies www.gnostice.com
---------------------------------------------------------------------
Gnostice eDocEngine (http://www.gnostice.com/edoc_engine.asp) -
Electronic document creation, PDF eForms and report export components

Gnostice PDFtoolkit (http://www.gnostice.com/pdftoolkit.asp) -
PDF document management and PDF eForms processing components
---------------------------------------------------------------------