Re: problem connecting to ADO programmatically

"William Meyer" <meyer.wil@xxxxxxxxx> wrote in news:4814ef19$1
@newsgroups.borland.com:

Chris.Cheney wrote:

FWIW I can reproduce your problem with the identical error message.

It seems somehow to be associated with "reuse" of the TAdoConnection
component. Try freeing it and recreating it before putting in the new
connect string.

Aaaarrgghhh....

It's a technique that's useful for when you have a non-design-time subclass
of a standard Borland component (e.g. when using the Turbo Delphi Explorer
product): drop the Borland component on the form and set it up as normal;
then at run-time instantiate the custom component, copying in the
properties from the Borland component; free the Borland component from the
form and assign the custom component to the form field.

So I will need to instantiate the components dynamically? Wow, I wonder
how long that bug has been lurking!

What a messy solution...

It's only a suggestion to try - no guarantees (but I would be interested to
know if it circumvents your problem). I'll have another look at it tomorrow
- I've been away today.

Does no-one else have anything to say on this?

Chris
.