M
muster
Hi all,
I probably have a misunderstanding of the use of a ADO Recordset.
I thought a Recourdset is a view and if I change it without updating
the underlying table (data) wouldn't change. But what I was
experiencing was different.
I opened a recordset with a select query of a table then manipulated
the recordset. Suprisingly I found that the underlying table (a linked
table from a SQL server) changed. Is this the normal way that a
Recordset behave? If so, is there an easy way to avoid it? I have
tried different combination of Lock type and Cursor type but did not
succeed.
Thank you for any hints,
I probably have a misunderstanding of the use of a ADO Recordset.
I thought a Recourdset is a view and if I change it without updating
the underlying table (data) wouldn't change. But what I was
experiencing was different.
I opened a recordset with a select query of a table then manipulated
the recordset. Suprisingly I found that the underlying table (a linked
table from a SQL server) changed. Is this the normal way that a
Recordset behave? If so, is there an easy way to avoid it? I have
tried different combination of Lock type and Cursor type but did not
succeed.
Thank you for any hints,