Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to trap COM instantiation
Message
From
31/07/2003 14:41:46
 
 
To
31/07/2003 14:16:47
General information
Forum:
ASP.NET
Category:
Other
Miscellaneous
Thread ID:
00815490
Message ID:
00815563
Views:
14
You must have only one declaration of:
>
>XceedZipLib.XceedZipClass loZipper
>
>
>The best way is to declare it at most local scope level - at the same level with statements, which use it.



Ok, so what is the "best" (or proper way) to test for the presence of any COM library/class/component if:
1. You can't trap for errors when it is instantiated due to scope change in try-catch.
2. It's not good practice (nor desirable) to declare the desired object twice.

Does one have to resort to checking the registry? It just sounds like a lot of work for something that I would think should be rather simple.


- Brian


VFP6 SP5, VFP8 SP1, VFP 9 SP 1 and Win XP SP 3 (unless otherwise specified)


www.wulfsden.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform