Prev: VB6's MSComm doesn't work well with Vista
Next: Toolbar caption wordwrap
From: Dee Earley on 17 May 2010 10:49
On 17/05/2010 15:17, jim evans wrote:
> Thanks much for your reply.
>
> On Mon, 17 May 2010 01:00:28 -0500, ralph<nt_consulting64(a)yahoo.net>
> wrote:
>
>
>> It will package the actual component used in the VB Project.
>>
>> Open up a VB Form file in a text editor and you will see the component
>> it is referencing and P&D will use to build a package.
>
> This is an example of what I see:
>
> Object = "{BDC217C8-ED16-11CD-956C-0000C04E4C0A}#1.1#0";
> "TABCTL32.OCX"
>
> I know which components are used/packaged, I just don't understand how
> to figure out where they are being taken from. Is there a way to
> decipher these references and figure that out without having to search
> the registry for each reference?

Wherever that file is registered unless the PDW files say to do otherwise.
You can normally see the registered path in the components window or the
object browser.

--
Dee Earley (dee.earley(a)icode.co.uk)
i-Catcher Development Team

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)
 | 
Pages: 1
Prev: VB6's MSComm doesn't work well with Vista
Next: Toolbar caption wordwrap