while i haven't used multiple tables linked in CR this way, I have used a single table with lots of data and a second table for options (a wizard generates the options and the data).

 

i am assuming that the report is set for ADO.net for the datasource and that you have linked the tables in the report. If they are unlinked, I would only expect 1 record as CR doesn't know how to advance through the record set.

 

Another way of looking at it, and this is if your report is called from an application...when the application calls it, it is not design time but run time.

If you never use an application, then you are probably always in design time as you can change the report.

 

I guess that is the easy way of looking at it, if you can change the layout or functioning of the report, you are in design time, otherwise you are in runtime.

 

so what I am asking is can you click on the preview button for your report and see the report as you envision it is suppose to be displayed. If the answer is no, then the report doesn't work. If it works when you hit the preview button, but not when you call it from the application, then one would suppose that the data being sent from the application is faulty, but if doesn't work in design, then it doesn't work and it is not the application...

 

so in short, I'm trying to determine where one should start looking to find the error.

 

 

stop the app right before you set the DataSource on the report.

use the variable.WriteXML("filename", writeSchema).

 

Now in the report, the datasource should already be ADO.Net, set the path to point at the file you just wrote out.  Now when you hit preview, the report will read the file, and you can start debugging.

 

if you change the datasource, you will need t go into Data Expert, right click your connection and refresh each table. Then go into the report and Verify Database...then when you preview, you will see your new data. 

 

HTH