Actually, workaround turned out not to work, so I'm still back at square one.

Here it is...

1) In VS.NET, I create an XSD with 3 datatables. Doesn't matter if I manually create them (by typing in the column names manually or pulling a structure definition from a table from server explorer)

2) Create a simple report in CR10, pointing to the XSD as the source for fields.

3) Go into VS.NET and write a small program that opens the CR10 file. The program populates a few test records for the data table, and then calls SETDATASOURCE for each of the three datatables.

The problem is that I get random 'object not set to instance' messages on different calls to setdatasource. The actual function generates a null exception in the system function 'DBFETCHROWSETFIELDS'.

Here's where it gets weird....if I do...

setdatasource(table1)
setdatasource(table2)
setdatasource(table3)

it bombs on table 3...if I reverse the order...

setdatasource(table3)
setdatasource(table2)
setdatasource(table1)

it bombs on table 1.

I thought, OK, maybe it just needs a 'stub' table at the end, so I did that, but it still bombs on #3. SetDataSource has a parameter of 3, the full syntax is...

SetDataSource(Table1,3,nTableNumber)

If I just pass two tables, it's fine...#3 bombs.

I'm guessing it's a coincidence that it's bombing on #3 and 3 happens to be the literal for DataTable, but it's a huge coincidence.

This all works fine when pointing to a cr.net report, but with CR10 it bombs. I thought I had this working last night, but I was mistaken.

At runtime, I even tried creating the datatable manually instead of pulling it from the XSD...no dice, same problem.

Kevin