Subject RE: [IBO] Sharing a connection between an exe and a DLL
Author Jason Wharton
Rob,

I'm working on it right now. Release notes are done already and I am again
working on getting the installer working for the C++ Builder side of BDS
2006. I've got it now where the installer will make it such that the
components are on both Win32 palette and the CPPB palette but I'm dealing
with a problem to do with the generation of the HPP file when compiling an
application there is an error for some reason. Apparently when compiling
the packages for inclusion in the IDE at design-time the HPP's are merely
generated but aren't necessarily compiled. The problem doesn't come about
until the actual HPP file is compiled when compiling an application that
makes use of it.

So, once i get this problem worked out the release should be out in a day or
two from that.

Jason


> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Robert martin
> Sent: Thursday, May 18, 2006 2:08 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] Sharing a connection between an exe and a DLL
>
>
> Hi Jason
>
> We are using an older version of IBOobjects so this problem probably
> isn't an issue for us. I have rewritten the dll to not use
> the shared
> handle and use its own connection for the time being. This is not as
> good of a solution but it should prove whether the issues we are
> experiencing are related to the dbHandleShared stuff or not.
>
> p.s. we are going to update to the latest version of your
> components as
> soon as we get this release of our application out (saves us
> retesting
> everything). When will the version with this fixed be
> available (roughly?)
>
> Rob Martin
> Software Engineer
>
> phone +64 03 377 0495
> fax +64 03 377 0496
> web www.chreos.com
>
> Wild Software Ltd
>
>
>
> Jason Wharton wrote:
> > There was a problem in the last release regarding this that
> will be fixed in
> > the next sub-release.
> > It has to do with making it load the client dll on demand
> rather than in the
> > unit initialization.
> > What is happening is your DLL is making API calls before
> the API function
> > pointers are pulled out of the Firebird/InterBase Client
> DLL. The fix was
> > to add a check to load the client dll when a handle is
> assigned to the
> > dbHandle or dbHandleShared property.
> >
> > Other than this problem, it should work fine as it did before.
> >
> > Jason Wharton