Yes, that had some positive effect.

However, looking a little closer, I now realize that I have a candidate key on the table being updated. Running in debug mode, I'm getting a 1884 error - duplicate candidate key, when trying to add to the selected list. I've created a new business object and put code in the presavehook of the selected business object to prevent duplicates from occurring. It still doesn't seem to solve the problem? It's still returning that error, in some cases, on the first record processed. Then, of course, it aborts the rest of the moves.

By the way, are you aware of any list that specifies the RETURN CODES that are returned when you try to a tableupdate or begin transaction? I'm getting a -3 back for the Begin Transaction and a -6 back from the tableupdate?

Thanks again for your input. I appreciate it!



>>They appear normal in the full list. Everything from the full list ended up in the selected list and everything in the selected list ended up in the full list??? They all appear normal after the move.
>
>Yeah, sounds like it's trying to move them in but can't because they're already there. Try changing the full list's RemoveType setting for selected items and see if the results appear correctly.
>
>Chris.