FiveTech Software tech support forums

The "MS-EXCEL button" enables only after exporting the report to MS-​​Word.

To see this problem, use the c:\fwh\samples\testrpt4.prg.

Thanks.

Oscar,

Once that gets enabled, does it properly export to Excel ? thanks

Linhares,

Only after I trigger another button into preview, the excel button is released and so I can export to excel.

Oscar,

Yes, the latest FWH reléase seems to have some bugs.

To fix this one, in the Rpreview.prg
In the Method Activate()

Insert the line
::oBar:AEvalWhen()

before the statement ACTIVATE window.

Lucas,

Mr. Rao is reviewing this issue. IMO It is not related to what you explain.

Thanks for your help anyhow

Antonio,

I haven't yet tested exporting to Excel with FWH 13.09 (just downloaded), but with the 13.08 version weird things would happen:

- The export would start at the the top of the report, but with some columns of data jumbled.

- The export would start a few pages into the printout, but with all columns of data showing corrrectly.

If you're not aware of this problem (maybe you are and it's already fixed), let me know and I'll post a couple of screenshots.

All the best,

- Roger

Roger,

Many thanks for your feedback. Mr. Rao implemented that code, I supervised it, and I am sure that Mr. Rao may be aware of those issues, if they are known to him.

As usual I prefer to know Mr. Rao opinion before making changing myself that all times are perfectly fixed by Rao

The "MS-EXCEL button" enables only after exporting the report to MS-​​Word.

This is fixed in FWH 13.10 to be released.

For now we may apply the fix suggested above:

in the Rpreview.prg
In the Method Activate()

Insert the line
::oBar:AEvalWhen()

before the statement ACTIVATE window.

Next issue raised:

I haven't yet tested exporting to Excel with FWH 13.09 (just downloaded), but with the 13.08 version weird things would happen:

- The export would start at the the top of the report, but with some columns of data jumbled.

- The export would start a few pages into the printout, but with all columns of data showing corrrectly.

There should be no problem with the rpreview.prg. I had used the feature hunderds of times without any issues with text data ( no images, no binary data, etc )

Please ensure the following:

1) oReport:bInit codeblock should clearly indicate the Restart for commencing generation of Excel output.

Typically we may say oReport:bInit := { || (cOurAlias)->( DbGoTop() ) } or similar statement to reposition the record pointer to where the export to excel should start.

2) Normally no complications should arise in case of MODAL Repreview. But in case of NON-MODAl preview, we should also take care that before export to excel is started, the default alias or recordpointers or any alias used in the report are not disturbed by any action in any other window. If we want to use export to Excel feature, it is highly desirable to use MODAL preview.

If you are still facing any problem even after observing the above, please post a sample program to reproduce the problem using any DBF in FWH samples folder. In case any other DBF has to be used to reproduce the problem. the same may be sent by email to Mr. Antonio and we shall examine at the earliest.

Thanks for your advice. I'll try it and let you know the results. All the best. - Roger