rowid won't work in a multiuser database. It's just the row number within the result set you retrieved. This sort of problem is the reason why people use a unique id field. The database automatically assigns you a number that won't change and isn't shown to the user (they can't change it either).
On 5/17/05, Will Leshner <[EMAIL PROTECTED]> wrote: > The problem is that the 'name' and 'age' fields are not sufficiently > unique to identify the very row the user wanted to update. Instead > every row that has matching names and ages are going to be updated. >