>The reason for me wanting a Modal Child Form is because there are certain forms that a user might access, in which they should "complete" using before attempting any other application function, as is the reason for any Modal form. The reason I want the form to be an MDI Child, is because I want it to appear to be apart of the application, and not just a floating window that can roam all over the desktop.

Ben,
The reason I asked was to get a better understanding of why you wanted to do what you want to do. I appears that the main reason you want a modal MDI child is so that the modal form stays within the app boundaries.
When I create an app I usually look at how M$ does their apps (because my customers are used to M$ software). I just checked the modal form scenario in Word (which is probably the most well known MDI app) and if you open a modal form (I used the font form) you can move the form all over (even over to my 2nd monitor) but you can not access any of the other MDI children (i.e. other Word documents).
So I guess I haven't really helped you at all, other than making you rethink your app design. I usually think that if the design is good enough for M$ then it is good enough for me (or my customers). If I develop similar to M$ I can also say to the customer that this is how it is done in M$ (and show him/her an example from a M$ product), and most customers say "Well if that is how M$ does it then it must be OK"
Anywho just my $0.02.

If you sill want to make the modal form a "MDI child" you could post your move code and me or someone else could try to make the "flicker" go away.

Einar