description: Hi
Firstly, thank you for a great piece of free software which works very well for me.
I think that I may have found a bug or maybe it is the planned behaviour.
I posted this as a question on stackoverflow here: http://stackoverflow.com/questions/30126619/only-1-row-in-recordset-but-all-rows-in-table-get-updated?lq=1
You may prefer to look at it there as it is better formatted than i can do here.

What it is is that I create a single row, single column recordset using this query:

sQuery = "select memo from clients where clientID = 10021 "

clientID is the primary key column.
Say the value in memo before update was 'bingo' then i edit and update it as follows:

rs.Fields("memo") = "blah"
rs.Update

Now every record in the table which had 'bingo' in its memo field gets 'blah' in there, instead.
I found that I could restrict the update to a single row by including the primary key in the list
of selected fields, like so;

sQuery = "select memo, clientID from clients where clientID = 10021 "

At first I was very surprised by this but it also strikes me as logical.
So, I don't know for certain if this is a bug or not.
However I can say that when I tested this using Access and Postgresql using ADO and ODBC the behaviour
was different. Just one row was edited.
Thank you for taking the time to look at this.
Jack

=>

Hi
Firstly, thank you for a great piece of free software which works very well for me.
I think that I may have found a bug or maybe it is the planned behaviour.
I posted this as a question on stackoverflow here: http://stackoverflow.com/questions/30126619/only-1-row-in-recordset-but-all-rows-in-table-get-updated?lq=1
You may prefer to look at it there as it is better formatted than i can do here.

What it is is that I create a single row, single column recordset using this query:

sQuery = "select memo from clients where clientID = 10021 "

clientID is the primary key column.
Say the value in memo before update was 'bingo' then i edit and update it as follows:

rs.Fields("memo") = "blah"
rs.Update

Now every record in the table which had 'bingo' in its memo field gets 'blah' in there, instead.

At first I was very surprised by this but it also strikes me as logical.
So, I don't know for certain if this is a bug or not.
However I can say that when I tested this using Access and Postgresql using ADO and ODBC the behaviour
was different. Just one row was edited.

I found that I could restrict the update to a single row by including the primary key in the list
of selected fields, like so;

sQuery = "select memo, clientID from clients where clientID = 10021 "

Thank you for taking the time to look at this.
Jack

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

Fix Version: 2.0.6 [ 10851 ]