🚀 go-pugleaf

I pulled an ADO example project off BDN.  I am puzzled by the following two
functions.

void __fastcall TForm1::FormActivate(TObject *Sender)
{
CoInitialize(NULL);
Form1->Catalog=Variant::CreateObject("ADOX.Catalog");
}
//--------------------------------------------------------------------------
-
void __fastcall TForm1::FormDeactivate(TObject *Sender)
{
CoUninitialize();
}

Yes, it is fairly obvious as to what they are supposed to do, but why place
calls to CoInitialize and CoUninitialize in FormActivate/FormDeactivate?
Does this provide any advantage or is it just a question of the style and
habits of the person who developed this particular example?

Would it not be better/safer to put calls to CoInitialize and CoUninitialize
in the constructor and destructor of a singleton class, instaniated in a
global static variable?  If I could do this, then I'd put the statement
"Form1->Catalog=Variant::CreateObject("ADOX.Catalog");" into TForm1's
constructor (and get rid of the unnecessary "Form1->").

Cheers,

Ted