: Neven MacEwan [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 18, 2000 12:02 AM
To: Multiple recipients of list delphi
Subject: Re: [DUG]: [Q] ADO / MDAC 2.6 / SQL7 Strangeness
D,
I some times think with ADO (and COM for that matter) in VCL type wrappers
there
are strange timing issues
PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Sent: Monday, 20 November 2000 10:03
Subject: RE: [DUG]: [Q] ADO / MDAC 2.6 / SQL7 Strangeness
You have got to remember that COM requires a message loop to function.
Also I had really funny bugs with ADO - there was lots of things
Subject: Re: [DUG]: [Q] ADO / MDAC 2.6 / SQL7 Strangeness
Myles
I understand the mechanisms - I just don't understand why the it says it is
'finished' (probably even fires an event to
say as such) and the object appears to continue changing asynchronously is
it (choose from the list)
1/ M
- Original Message -
From: Donovan J. Edye [EMAIL PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Sent: Friday, November 17, 2000 5:07 PM
Subject: [DUG]: [Q] ADO / MDAC 2.6 / SQL7 Strangeness
G'Day,
Env: Delphi 5.01, Informal MDAC 2.6 patch installed, MDAC 2.6, SQL7
G'Day,
Env: Delphi 5.01, Informal MDAC 2.6 patch installed, MDAC 2.6, SQL7 SP2
I seem to be one of the lucky ones (not!!!) that "lost" all sensible error
reporting once upgraded to MDAC 2.6. I am now faced with hex values for
errors and not too friendly error strings. That aside. I have the
