Thanks, that's what I found out and I played with it yesterday. It was all in the help file. Didn't know it was there until I looked up WriteXmlSchema that you sent me.

myDataSet.WriteXml(C:\Temp\ChargeBacks.Xml, XmlWriteMode.WriteSchema)

This I put in my code after I get the dataset. This can be remmed out or set with a testing flag since it's not needed in the live application.

Then you can point to the .xml file. You have to create a new connection in ADO.NET (XML). It seems to take on the business object's name, NewDataSet\repolist, but you can change the repolist to something more clear like 'ChargeBacks'.

The file has all the data in it from the dataset, but you have to have the 'WriteSchema' set, else you can't format the fields correctly in Crystal Reports.

I've also found that seeing the data in Crystal Reports is a hit and miss thing. They're there, and sometimes they're not, and you have to save the the report to get it back, and so forth. I haven't found the right formula yet, but eventually you will see the data which really helps in creating the report.

You also have to make sure that all the fields are there in your stored procedure and in the dataset, else you have to start over. Again I haven't figured out the best sequence to use for this method. You can't delete a connection, however, if you have to create a couple or more of them, and you don't use some, you can shut the environment down and they won't appear the next time you start up. A bother true, but maybe VB 2008 will fix this.

So now I have to change all my 20 reports...ah, sigh, but my SQL Server people will be happier.

Thanks again. CU