>

Are you sure it's not just a garbage collection issue?
>I've had the same problem with Adobe Acrobat until I double-checked the order I was destroying the objects.
>Once I adjusted the order so that it released the objects in the opposite order I instanciated them, the problem went away.
>

>
>Paul,
>
>I just started using the MM's Drag-and-drop functionality and I only tried the Project Manager Sample Application that comes with the Framework. It would surprise me that Kevin didn't think about that but I'll check this out.
>
>Do you mean you used MM's Drag-and-drop functionality without this error?
>
>Mark

No, I haven't used the drag+drop stuff in the framework. I just took a quick look at the class and there is only one object to be cleaned up, which is done before calling DODEFAULT(). I've used drag+drop in another app, but don't remember running into any C5 errors (although it wouldn't surprise me if there were problems with it), but since it's only C5ing on exit, it really sounds like a garbage collection issue. The really nasty part of diagnosing those kinds of problems is that they're so hard to track down. Sorry I can't be more helpful.