I have been using SQL RS for a few weeks now - great product and easy to design reports in. The designer is a little clunky but what do you expect for free. I have however noticed one big glaring hole in the product as follows:<BR><BR>When using Crystal reports, you could create a dataset (.NET dataset) on the fly and modify/calculate and otherwise modify the data programatically then pass the dataset to crystal as a datasource and wa-la! You have a very sophisticated report.<BR><BR>SQL RS seems to be able to do all the normal basic reporting functions of Crystal but you can't pass it a dataset! All you can do is create/manipulate the data within a report. I have worked out a process by which you could create an XML file from the previous example (.NET dataset) and then via a new SQL RS extension, point your report to the XML input file and hence "pass it the dataset as a datasource". Seems a little goofy to do it this way when using a .NET dataset as a datasource (via a webservice or some such thing) should really be part of the product.<BR><BR>Does anyone else have any thoughts? Maybe I'm missing something? There is always a better way to do something - does anyone have a better way?