At 10:53 AM 10/04/2006, you wrote:

> > A bit off-topic for this list, but pay attention to the following
> > when using the IBOAdmin components:
> >
> > 1) if you're mixing a service component with a data access
> > application, don't be fooled into thinking that the service
>component
> > will jump onto a valid connection that you have already made to a
> > database. The service components create their own IB_Connection
>from
> > the properties you set in Server, DatabaseName and Protocol in the
> > service component. Protocol must be cpTCP_IP. Under the hood, it
> > will all be converted to a remote service_mgr attachment, the only
> > kind that works for Classic.
> >
>
>My Protocol is cpTCP_IP.
>
>I am getting error "Lock time out on wait transaction"

That, combined with the "difficulty" that you might be having with
the database handle (your original supposition) suggest that you *do*
have unclean entries in Params, i.e. Params is defaulting to a local
connection and passing the wrong stuff over the wire.

FWIW, I do recall having that problem with the IBX service components
which, of course, use the server portion of the string to find the
service_mgr, and then invoke gbak locally. The Borl components don't
know anything about Classic, except that it's not supported by the
Services API. So they do some horrible diddly-widdly stuff with the
embedded versions strings and arrive at the conclusion that you are
trying to do something wicked. If you have an old version of
IBOAdmin, you could be encountering the same bug. Lorenzo did fix
that, quite early in his development of the IBOAdmin components, but
it's worth checking both your client libraries and the age of your
IBOAdmin comps. The ones I have (that work with Classic) have
IBOAdminReg.pas dated 24/11/2003.

Also check that you have the right firebird.msg file for your version
of everything else.

> > 2) clean out all the cruft that gets written into the Params
>property
> > at design-time. Otherwise there's a high chance that your previous
> > wrong settings will just sit there waiting to bite you at runtime.
> >
> > ./heLen
> >
>
>I only set Username and password parameters.

1. Try performing a Params.Clear, followed by a Params.Add() to "add
back" the username and password.

2. Double check to make sure that the service_mgr is finding
fbclient.dll in the \bin directory of the database (or in the default
system path, if that's how you are working things)

3. And, as always, check the version string of both gds32.dll and
fbclient.dll. They should be the same as each other and have the
same build number as the server.