Linda,

Thanks for your suggestion, although I believe the problem might not have been about a unique key. Either way, I got around this by using a different solution by using a view that did not use a group by clause. I then grouped the values in my code while looping through the data.

I am guessing the group by caused a column to be defined in some manner that could not support the result set in the class itself. As I had mentioned previously the view got returned fine in SQL but not in the object.

One day, I will look deeper into this, when I have some free time (or when this error happens again perhaps).

Bob

>Bob,
>You may want to just generate a unique key for your view. I think that might get you past this error. I have gotten that a few times when using views with business objects and that seemed to solve the problem.
>The other option is to create a new dataset, turn the constraints off on that and set the biz object's current dataset to the new dataset. Sample code is below.
>
>

>            DataSet ds = new DataSet();
>            ds.EnforceConstraints = false;
>            this.FillDataSet(ds, StoredProcedureName, TableName,
>                param1, param2, param3);
>            this.SetCurrentDataSet(ds);
>            return ds;
>

>Linda
>