only behaviour for a DataTable
The point being that the DataSet is *always* disconnected. An ADO
recordset
is, by default, attached to the database, so the notion of read-only was
rather more important. With a DataSet any changes that happen to be
made
will not actually have any long term ef
The point being that the DataSet is *always* disconnected. An ADO recordset
is, by default, attached to the database, so the notion of read-only was
rather more important. With a DataSet any changes that happen to be made
will not actually have any long term effect unless something explicitly
pu
Don't think there is anyway to prohit another programmer from changing the data in a
datatable.
-Original Message-
From: Greg Gates [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 2:27 PM
To: [EMAIL PROTECTED]
Subject: [DOTNET] Read only behaviour for a DataTable
Hello everyone:
In "classic" ADO, the ADO recordset had a clone method to which you could
pass a lock type. One of the lock types was adLockReadOnly. Thus it was
possible to return a reference to an existing ADO recordset and have read
only behaviour.
What is the best way to allow a client to ob
