🚀 go-pugleaf

Hi,

Did you try Component \ Import Component and Import ActiveX control? That 
should give you the option to import the control and add it to a package.

Graham

"David CS Roberts" <dcsrobts@wfubmc.edu> wrote in message 
news:44e9ae4a$1@newsgroups.borland.com...
>I am porting to D2006 a Delphi7 program which contains a 3rd party ActiveX 
>component
>
>
>
> D2006 (Delphi for Win32, VCL Forms application)  tells me that it does not 
> recognize the component and asks whether I want to delete it and loose the 
> associated code. (Not a good option).
>
>
>
> I have tried to add the .ocx component to the ActiveX tool palette but for 
> some reason the ActiveX section is not listed in the Tool Palette. 
> Interestingly, if I open a new C# Project (Windows Forms Application), the 
> ActiveX tool palette is there and it contains my 3rd party component. But 
> no matter what kind of new Delphi project I open, the ActiveX palette 
> disappears. I have also tried putting the component in another palette, 
> but that doesn't seem to work and it is never visible.
>
>
> What am I missing?
>
>
>
> 

Yes, I did Import the ActiveX component, but the tool palette still shows me 
just about every other palette exept the ActiveX.

However, I have made progress. My project has several units and forms (one 
of which contains the 3rd party control). Interestingly, when I open the 
Main form of my Delphi7 project in BDS2006, it converts/updates the project, 
compiles it without problem and runs it. The subordinate form with the 3rd 
party I/O controls are visible and work fine.

The problem arises when I try to open the subordinate unit and form. DBS2006 
pops up an error box which says that "class TActiveIO_PortDisplay not found" 
(the 3rd party ActiveX component) and doesn't show the form. I can't, 
therefore work on this part of the project.

I am totally surprized that it compiles and runs as long as I don't open 
that particular unit.

Thanks for your help.


"Graham Neden" <graham@starfish.tv> wrote in message 
news:44eb1f75$1@newsgroups.borland.com...
> Hi,
>
> Did you try Component \ Import Component and Import ActiveX control? That 
> should give you the option to import the control and add it to a package.
>
> Graham
>
> "David CS Roberts" <dcsrobts@wfubmc.edu> wrote in message 
> news:44e9ae4a$1@newsgroups.borland.com...
>>I am porting to D2006 a Delphi7 program which contains a 3rd party ActiveX 
>>component
>>
>>
>>
>> D2006 (Delphi for Win32, VCL Forms application)  tells me that it does 
>> not recognize the component and asks whether I want to delete it and 
>> loose the associated code. (Not a good option).
>>
>>
>>
>> I have tried to add the .ocx component to the ActiveX tool palette but 
>> for some reason the ActiveX section is not listed in the Tool Palette. 
>> Interestingly, if I open a new C# Project (Windows Forms Application), 
>> the ActiveX tool palette is there and it contains my 3rd party component. 
>> But no matter what kind of new Delphi project I open, the ActiveX palette 
>> disappears. I have also tried putting the component in another palette, 
>> but that doesn't seem to work and it is never visible.
>>
>>
>> What am I missing?
>>
>>
>>
>>
>
> 

"David CS Roberts" <dcsrobts@wfubmc.edu> wrote in message 
news:44ec66b6$1@newsgroups.borland.com...
>
> I am totally surprized that it compiles and runs as long as I don't open 
> that particular unit.
>
> Thanks for your help.
>
>

The packages installed in the IDE are generally design time packages and 
contain code that registers the object classes.  These classes are used to 
create instances for you to see at design time on the form IF the form is 
loaded up.  If you don't load the form to see the objects on it, the design 
time package isn't needed.  All the required USES clauses suck in what is 
needed at compile time.

Consequently, the compiler is happy as long as it finds DCUs to link in for 
the uses clause that match the version of the compiler.  If it doesn't find 
them, it looks for source code to see if it can build them.  If it can't 
find them, you get a whacko message about it not finding the DCU (I think) 
which confuses you if you look and can see that the DCU exists (but is wrong 
version), but it is really looking for the PAS in order to compile a current 
version.

So as long as you don't display the form, the design time libraries are used 
and the missing BPL won't be missed.  Only when you display the form and the 
instances need to be created will the IDE discover that the BPL is missing.

Hence the error messages on object classes it can't create.