Re: problem connecting to ADO programmatically

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....

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

What a messy solution...

--

Bill
.

Relevant Pages

  • Re: TADOConnection opens in design time
    ... function GetConnectionString(ConnectionString: string): string; ... ADOConnect: TADOConnection; ... "Brian Bushay TeamB" wrote in message ...
    (borland.public.delphi.database.ado)
  • Re: modern classical guitar for early music
    ... >any thoughts on the playing of early music on a modern, 6 string ... >classical guitar - recreating the music as opposed to reenacting it? ...
    (rec.music.early)
  • Re: Free TList problem
    ... String indexes, even for short strings begin at 1. ... not freeing the individual records that it might have contained? ... shouldn't you be freeing ... You could avoid pointers and TLists by using dynamic arrays ...
    (borland.public.delphi.language.objectpascal)
  • modern classical guitar for early music
    ... any thoughts on the playing of early music on a modern, 6 string ... classical guitar - recreating the music as opposed to reenacting it? ...
    (rec.music.early)
  • Re: CString::AllocSysString() needs to be freed?
    ... the caller of the function is responsible for freeing it. ... foo is accessing a database via ADO. ... > Do I need to free the memory allocated to string or will it do so ...
    (microsoft.public.dotnet.languages.vc)