hopefully someone out there is using the CrystalReportViewer besides me and can give me some feedback. i've literally been on the internet for weeks looking at all sorts of approaches, all sorts of code that exports the data once it displays inside of the control.
suffice to say, i'm passing a dataset to the report source and displaying it in the CrystalReportViewer Control that comes w/ VS 2003.

im curious - in the .rpt itself in the database expert, is everyone using the Default "NewDataset" which uses the .xsd schema path?
when i use that, it displays in the CrystalReportViewer, but the contents won't export, i simply get the Header and Footer (if any is used)

However, if i write to say the C:\drive.........
myDataSet.WriteXML("C:\myReport.xml").... and then change the datasource to reflect that path and a .xml rather than .xsd schema, the CrystalReportViewer displays exactly the same, and it will allow export to .pdf, .doc or .xls - no problem.
i thought the idea was to use the Schema structure to display the result of the dataSet in the CrystalReportViewer.
i've seen and used ALL of the code examples here for exporting and my Instance of the .rpt is declared Public so scope isnt an issue here.

so, which is is folks? .xsd or .xml in the Database Expert. Note* i am passing a new dataset at runtime.
thanks for any help or advice. i can make it work for display and export but, only if the datasource is .xml inside the Report1.rpt.
thanks
rik


**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

reconcile db-changes back to dataset
Why won't my DataTable.Update?
note getting returned data and asp.net 2
Selecting, Inserting and Updating Relational Data (SQLServer/ADO.NET)
Updating - let me count the ways