Einar,

That's basically correct. In a nutshell, here's the approach I use (not to say it's the only way, but here's the method I've used for years)...

1) Design your report data structure as a strongly-typed Dataset using VS.NET. So your schema might have 2 tables...DtHeader and DtDetails. You might call the DataSet DsInvoices.

2) Generate the schema in VS.NET...it'll create a file called DsInvoices.XSD

3) Design your report in Crystal...for the data source, there should be an option for ADO.NET/XML...look for DsInvoices...then you can lay things out however you wish. (I don't know if you're using the designer in CR.NET or if you're using CR9 or CR10. I think there might be slight differences between the two. If you're doing it in CR.NET, you probably can reference the typed dataset directly. If you're using CR9 or CR10, you'll want to point to the XSD)

4) At runtime, you need to pass a set of data tables that are basically identical in structure to Crystal, using the function call I mentioned earlier.


Kevin