>>But events are still events :-}
>>If the method containing the MoveTo() is triggered by an event then it's possible that a new call will tread on an existing one with obvious consequences. If that's a possibility then putting a lock on the method might be a solution.....
>
>It is not an event.

Then, assuming the file is actually moved (and that you are catching any exception raised by the MoveTo()) I guess we are back to your first supposition that this is simply a timing issue. Maybe a short Sleep() before getting DirectoryInfo() ?

I was just trying to think of other possibilties......