>Hi Tim,
>
>I don't even know what you mean by a read-only DataSet! How can it be read-only? Do you mean the property that holds the DataSet instance is read-only? Are you using a Framework or is this straight ADO.NET? TableAdapters or DataAdapters?
>
>~~Bonnie

Hi Bonnie,

I am posting this because I am trying to help a client programmer but I am not at home where I can look at any of my code. He had problems with the DataSets when running against the two different stored procedures. When debugging he found one to be read-only. I assume that was a property of the either the dataset or the table within. Yes the framework is MM but I don't think (will check when home) there is anything in the framework that sets that and possibly it is detected because the stored procedures are different. I will look at it directly myself when I get home and see exactly what is going on. I had hoped there was a simple answer on how to force a dataset to be read-write.
Thanks
Tim

>
>
>>Hi all,
>>
>>We have two different stored procedures to retrieve data into datasets. The way the selection criteria differs but other than this the data retrieved is identical for tables, columns and such. One of the stored procedures when we fill a DataSet is readonly and the other is read/write. I was under the impression that all DataSet's were read/write by default. Any idea if there is something in the framework that determines to make a DataSet readonly? Is there a way around this?
>>Thanks
>>Tim