Its ADO.NET that is putting the 1 or 2 at the end of the table name. For now I think you are going to have to clear them yourself before you make the call to FillDataSet.

DataTable dt = this.GetCurrentDataSet().Tables["Customer2"];
if (dt != null) dt.Clear();
//continue with call to FillDataSet...

When you think about it, how can MM.NET really know how may tables are returned from your stored procedure? I agree that it would probably be a good enhancement for the framework but might take some fancy footwork to get the coding right.


>Jason
>
>I don't think you understand the issue. When you call a store procedure and it return more than 1 tables and you pass "Customer" as the table name, the framework automatically name the tables "Customer","Customer1","Customer2", and so on. When we make that store procedure call twice with ClearOnFill = true, only table "Customer" was cleared first and contains the result from the second call. "Customer2" contains the records from the second call PLUS the records from the first call. We are wondering if this is the correct behavior.