Let's see if I grasp what you're doing:
- opening a form which has open or load event and in that event you are opening a second form
- in the 2nd form open or load event you are trying to close the 1st form
- you are wondering why any code in the 1st form that hasn't executed is still processing even though you demanded that it close?
If that's correct, then it is to be expected. Unless you have some sort of abnormal close of either the db or crash of a form, don't expect unfinished code to terminate just because you initiate a close command from somewhere else. This behaviour is commonly reported when someone cancels a form open event and the form that called it complains that the event was cancelled. If memory serves, that is error 2501?
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.