Hi Ashley,

I don't debate your arguments for the creation of an FRX to XLS utility. But there are other ways to do it, customized, in VFP code. By nature, an FRX to XLS class would have to be generic. And that would neccesitate large amounts of custom code. The beauty of FRX2Word is that it requires *zero* custom code to deliver immediate functionality.

>
>Thought I'd jump in here as I have had the need to provide Excel as an export format:
>Users will always find creative ways to use the data your report:
> Feed another spreadsheet of their making (changes with the phases of the moon)
> Create a custom graph or set of data which is unique to their location.
> Create a spreadsheet for one-time statistical analysis.
> Create a spreadsheet because their imagination is several-fold greater than our own.
>
>Using COPY TO .. XL5 has its limitations: formatted, calculated fields which would need to be stored to a cursor mirroring the output. It also results in ugly output.
>
>The VFP community are grateful for the utility.
>
>Regards
>
>>Hi Mario,
>>
>>I (the originator of Frx2Word) entertained the idea of Frx2XLS (as I called it) last year. I didn't see the end value, though. If you want to move data to Excel, then there must be a calculative reason. So what would be gained insofar as font settings and formatting would be secondary to whatever reason you were moving to Excel. In which case, the COPY TO or EXPORT commands would suffice.
>>
>>
>>>I know the class Frx2Word, but, dont exist Frx2Excel?
>>>
>>>Thank.