Bypass Child Form Closing In .NET To Get Same Behavior As VB6?

VB6 application MDI-Child architecture. Closing event is handled via QueryUnload event in both MDI and child form. Order of event trigger is MDI form closing(QueryUnload) event fires first followed by child form closing event(QueryUnload, I would like to call it as FormClosing itself as it is more comfortable and correct)Now after migration, order of event trigger is occuring in reverse. Child form closing event is firing first followed by MDI form closing event. We want to reverse the event triggering badly because of the logic written inside the closing events. Swapping the logic inside the events is not a viable option considering the huge changes we need to make (we have 31 vbprojects with 31 MDI forms and numerous child forms).

How I can make the MDI's closing event to be triggered first before child's closing event?