FWIW, I *believe* that you'd only need to distribute the appropriate object
library files (.olb's), which are mostly just interface definitions--there's
no actual code in them.  (In fact, I don't think you can legally distribute
the corresponding .dlls).  So... it may not add so very much to your
control's install.

Anyhoo, I'm happy to have been of service.

Cheers,

-Roy

Roy Pardee
Programmer/Analyst
SWFPAC Lockheed Martin IT
Extension 8487

-----Original Message-----
From: Ron Howerton [mailto:ron.howerton@s...]
Sent: Wednesday, November 14, 2001 12:04 PM
To: professional vb
Subject: [pro_vb] RE: Checking existence of a specific property in obj
ect collection


Roy,

Yes, there is a difference!  Your solution is much cleaner than mine for 
determining whether I'm looking at an Access form.  I found that I had to 
include a reference to the Microsoft Access library in my ActiveX project 
in order to compile, because it kept choking on "Access.Form".  I wonder 
how this might work on a machine that does not have the Access library, 
then?  Perhaps I could wrap it in an error handler and assume I'm in the 
VB world if it stumbles over that statement in execution.  Or I suppose I 
could just automatically include the library with the install and avoid 
the issue, although VB programs come with so much unnecessary overhead 
already.  In any case, thanks for your suggestion.

> Is there any difference if you explicitly reference the lib from which 
Form
> comes?  That is:
> 
> If TypeOf UserControl.Parent Is Access.Form Then...
> 
> (or VB.Form, as you like).
> 
> -Roy
> 
> Roy Pardee
> Programmer/Analyst
> SWFPAC Lockheed Martin IT
> Extension 8487