Nate,
The clearOnFill flag is a signal to clear out any previously existing version of only the specified table in the dataset, so that it can be replaced with the new one. I'm suspecting Kevin did it this way to prevent other tables in the dataset from being wiped out when only one is being updated (which is a good thing for those of us setting DataRelations), but he'll have to confirm that.

There's also GetEmptyDataSet() at mmBusinessObject, if that helps... it also fires the same hooks and raises the same events that FillDataSet() does.

If that doesn't work, we may be able to talk Kevin into adding a new parameter or a new field (something like mmBusinessObject.ClearOnFillDataSet) since he'll be in a great mood after his restful Irish trek... that is, unless they make him fill in for Michael Flatley again on the Riverdance tour!

Hope that helps and sorry for the visual,
---J

>I have a business object (inherited from mmBusinessObject) that uses a stored proc in SQL server in it's call to FillDataSet(). This stored proc returns several tables in a dataset. When I issue a subsequent call to FillDataSet, with the clearOnFill parameter as true, the first table in the dataset is cleared just fine, but any other tables in the dataset do not get cleared, they just get appended with the new data.
>
>I can get around this by calling DataSet.Tables.Clear() prior to filling the DataSet, but I assumed that this is what the clearOnFill parameter was used for. Am I doing something wrong or is this something to be addressed in MM? I'm using version 1 of MM.
>
>Thanks,
>
>-Nate