>>
>>Metin,
>>
>>Yes we can use that too but what customer want is 100% the same with the report output. That's how .net report works.
>
>This is exactly what XFRX does, and this is more or less only way it can be done. By creating myriad of columns / rows.
>This is due to nature of excel, and nothing can be done about it. (Unless you export it as pictures)
>Do you want to tell me that in NET/SSRS reporting you can create complex report (absolute positioning for instance) and have it exported to distinct excel rows/cells directly ??

Yes. In NET/SSRS reporting, it converts report to Excel format the way expected it to be. Of course the formulas are not available, but the positioning in columns/rows or the exact cell is to me acceptable and way way beyond what XFRX does.

>
>I use XFRX for some report exports, but when it comes to excel I code my reports using excel wrapper class in order to take full advantage of formulas, subtotaling, autofiltering etc. Otherwise I see no point in exporting report to excel.
>If it is just for emailing/printing purposes then PDF is much better option, if it is for further processing/caculations in excel
>then there is simply 'no free lunch'. You either do plain export as Metin does, or roll up your sleeves and create
>custom shape excel report. What I normally do is use predefined excel template with certain forumulas and formatting
>already in place, and then just poke data into predefined sections. Results you get is much more valuable then any printed report can possibly give you. Your users are just going to love you for this :)

You have a point, but you can just imagine creating excel template in every report i wish to convert? I don't know the exact reasons why customers are asking for this feature. And we're saying sorry so far if we can't do it in VFP apps. These projects are legacy apps at best because we already stopped deploying VFP apps starting half of this year. But the VFP app was deployed in over 130 hospitals nationwide as opposed to 10+ .Net app deployment.