Using ROWIDs to perform DML on records can be wicked fast, and is virtually the fastest way to access a row.
However, if there is any chance that someone else's operation (and even yours) can alter the ROWIDs of a table, you can find yourself with lots of messy data.
How can the row be not located when there is only ONE record in the table?
Some values may have been changed since it was last read. Simeonstr SQL ="update My Table set h Asof = 'As of " & Format(Date, "mmmm dd, yyyy") & "'" _ ", h Printed By = 'Printed by: " & User "'" & _ ......
First, let's get a record of the current ROWIDs for each office and then delete two rows.
Interestingly enough, the ROWIDs for the two remaining rows are different from their original IDs before the delete statement.
A simple alter table statement remedies the update problem. Well, tables are partitioned for a reason, and to help ensure data goes where it is supposed to, you should disallow inadvertent updates or row movements.
Some values may have been changed since it was last read." The same code was working with SQL 2000 !!! Please give us something more to work with, and I'm sure that someone will try to help...
Recordset Deyt = "As of " & Format(Date, "mmmm dd, yyyy") !
As far back as Oracle 8.1.5 documentation, row movement applied to updatable partition keys.
A list partition where the partition key is a specific value is a good example of this.