1 In the web browser you can output to delimiteddata, if you add &mimetype=application/vnd.ms-excel the browser should open the data in excel automatically.
2 We also use an output type of SIMPLEEXCEL, there is not much documentation on this though. This outputs to excel in roughly the same format as the pdf shows (i.e. headings, shading, totals etc). You have to play around with the layout a bit to make it look really good though.
I an use delimited as desformat. But for some of the reports having number of columns around 20-23 its giving me blank page,though i am getting correct format o/p in htmlcss format.
Any suggestions as to how to convert htmlcss o/p to xls.
I've done Excel output using the Microsoft XML Schema for Excel. This works well as long as you don't mind the files being bigger, and you're very familiar with XSLT
Your report would then generate output to XML, and you create an XSL that turns it into an Excel XML file. Note this requires at least Excel XP on the client, but you can do almost any formatting you want - fonts, colors, borders, even cell formulas and notes!
See http://www.microsoft.com/office/xml/default.mspx for the XML schemas. All the docs say it's for Office 2003, but we've used it for over a year with Office XP with no issues.
I have application servers of 10g rel 1 (904).
it is a test server. I'm generating reports in that server in .xls format. But the problem occours in generating the report when the data is less then 1 Kb.
We got a "page cannot be displayed" problem in 10.1.2.0.2 when had SSO turned on and a form created a reports parameter .html file and then that tried to call the report. Turned out that the form could make the .html file and then open it using the URL :
but, when the post form action of the .html file also tried to use this URL to open the report it failed. (Note, each browser pc already had a Windows "hosts" file set up with the host name mapped to the IP address AS box name).
We had to change the post form action's URL to:
ie had to put the full domain name there.
Infact, even just "http://host.domain/reports/rwservlet?" (no port number) worked. That was probably because we were using the default port anway.
Finally realised that the full "host.domain" name was the name that we registered as the host name - when registering with the OID. This was when we first installed AS. Looks like SSO needs "that" registered host name.