Anyone ever run in to this issue I'm seeing... I have some code that
adds an appointment item, then calls Move to move it to the correct
folder. Most of the time it is already in the correct folder, so the
"Move" really doesn't do anything. Under previous testing, Move would
return an error if the item was already in the correct folder. Now,
on at least one test system, running Outlook 2003, it appears Move
creates a Copy of the appointment item, instead of returning an error.

The obvious thing would be for me to not attempt to move the item if
already in the correct folder, but that requires changing my design
and a lot of existing code. I'd like it at least understand why this
change may have occured (in Outlook 2003? or a service pack?) before I
go making changes designed around this new behavior.

On Feb 25, 11:32*am, eric wrote:
Anyone ever run in to this issue I'm seeing... *I have some code that
adds an appointment item, then calls Move to move it to the correct
folder. *Most of the time it is already in the correct folder, so the
"Move" really doesn't do anything. *Under previous testing, Move would
return an error if the item was already in the correct folder. *Now,
on at least one test system, running Outlook 2003, it appears Move
creates a Copy of the appointment item, instead of returning an error.

The obvious thing would be for me to not attempt to move the item if
already in the correct folder, but that requires changing my design
and a lot of existing code. *I'd like it at least understand why this
change may have occured (in Outlook 2003? or a service pack?) before I
go making changes designed around this new behavior.

Nevermind, turns out I wasn't debugging this issue correctly and this
wasn't even what was happening.