Well, it seems I've run into MSKB article Q177135 (ODBC stuff in DLL global scope causes GPF "by design".
Now I am left with the task of removing a global database object, while retaining global access to it, and without breaking current function compatibility (which means moving to a class is out, as is adding the database as a parameter for all functions).
Um.. help? Suggestions?
---Evil Peer
Now I am left with the task of removing a global database object, while retaining global access to it, and without breaking current function compatibility (which means moving to a class is out, as is adding the database as a parameter for all functions).
Um.. help? Suggestions?
---Evil Peer