I have several programs that use Excel and/or
Access objects fairly heavily. When a program
crashes for whatever reason, these objects are
left open (usually invisible).
Is there a secret to closing these objects when
a program crashes?
Printable View
I have several programs that use Excel and/or
Access objects fairly heavily. When a program
crashes for whatever reason, these objects are
left open (usually invisible).
Is there a secret to closing these objects when
a program crashes?
Hi,
I can give you a "touch your nose by taking your hand around your head" method!:-)
(Translated literally from my mother tongue, an Indian language)
Wrap all your Excel & Access objects in Activex server classes and let your program talk with these (created by you) server objects.
This way you are introducing another layer. You can deligate a little bit of processing into them also, there by achieving "distributedness" in your design!. Desing them to start and end neatly.
If your (client) program crashes for some reason, these server objects will be deleted automatically, i.e when the last client program exists - so OS will do it for you (supposedly).
They call these as "extender classes" i think!.
Like somebody in another posting said, "it is only an idea, dont take it to bank" :-)
Ravi Kiran