At 09:22 PM 22/06/2006, you wrote:

>Helen, Thanks for your reply
>
>Firstly, my apologies for not noticing your reply earlier amd
>subsequently posting a message saying I'd not had a reply.
>
>I have followed your points (below), with no success.
>I don't have 18 bpl files. I have 9. All of these BPLs are on BDS2006
>specified paths, identified under BDS2006 Options as:
> Library Paths,
> Package OutPut directory
> DCP output directory
> Browsing Path
>
>The 9 BPLs I have are
> IBO40ADT_D2006.bpl
> IBO40CDT_D2006.bpl
> IBO40EDT_D2006.bpl
> IBO40FDT_D2006.bpl
> IBO40TDT_D2006.bpl
> IBO40VDT_D2006.bpl
> IBO40WDT_D2006.bpl
> IBO40WXDT_D2006.bpl
> IBO40XDT_D2006.bpl
>
>I have 18 DCU's, 9 of which have correspondingly named BPL's

Search your hard disk for the other 9 BPLs. They have names like the
above except with 'RT' (for run-time) where those ones have 'DT'
(design-time). The most likely place is system32 but, if they aren't
there, search through your BDS directories. They will be
*somewhere*, since the design-time libs couldn't have compiled without them.

>I can't figure out why there should be a mismatch.

There's not; except that there is no "ERT". The "EDT" package is
the design-time editors (i.e. property editors).

>Being very new to IBO, I have no good idea how the installation
>process works and whether compiles and builds are performed at
>installation time. If compilations are done at installation time, I
>would have thought I would see one or two error messages.

They are done at installation time and you wouldn't see error
messages if there were no errors. The *installer* knew where it put
things. Your unfortunate challenge is to find the pieces it didn't
tell Delphi about.

>Thanks for your suggestions

When I say "search", I don't mean an eyeball search in possible
likely places. I mean, use the Windows search applet with wildcards,
i.e. IBO40?RT_D2006.bpl

Helen