>>Well, I got it working with a cursor. The problem is that I have to take the buffering off the table for it to work. Although, now that I think about it, it shouldn't be a big deal because the way it's set up isn't very conducive to saving/reverting anyway.
>
>Good, I prefer the cursor method myself...and it'd no big deal to set buffering off, do SQL, and buffering back on again if you need to...

Not sure how that would work... The problem is that with buffering, the records aren't actually in the table for the SQL to act on. Wouldn't you have to commit the changes for it to work? What does turning buffering off when there are uncommited changes do?

Thanks,

Michelle