Re: Getting OLE Error 800A0E7F
- From: "Bert Moorthaemer" <nospam.bert.moorthaemer@xxxxxxxxxx>
- Date: Thu, 22 Dec 2005 09:17:48 +0100
Guillem,
> have you tried to update your ODBC driver? I've found a reference to
I have the lastest version of the ODBC drivers (2 weeks old)
>You should also try updating your MDAC if it's not the latest version.
I will check and update if nessacery
> do you also call coUninitialize after ending the work? it could have
I do
Bert.
"Guillem" <guillemvicens-nospam@xxxxxxxxxxxxxxxxxx> wrote in message
news:xn0eb9b8j2f0ms000@xxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Bert Moorthaemer wrote:
>
>> Hi all!
>>
>> I have an application that retrieves and updates data from a back-end
>> database connected through the OLE DB ODBC driver.
>
> have you tried to update your ODBC driver? I've found a reference to
> this problem with MyODBC (for MySQL). You should also try updating your
> MDAC if it's not the latest version.
>
> for MDAC:
> http://www.microsoft.com/downloads/details...&DisplayLang=en
>
>>
>> I use the ADO components of D7 update 2
>> I have setup the connection to be used in non-asynch mode and I use
>> standard TADOQuery's to do the retrieval and updates. The update and
>> retrievals are done using threads (and yes I have called CoInitialize
>> when starting the execute loop)
>
> see below
>
>>
>> The problem is:
>> I regulary get this error: OLE Error 800A0E7F (which seems to be:
>> operation not allowed in asynch mode) This happens more on updates
>> than on retrievals. This error is directly followed by an access
>> violation. I have checked and double checked memory allocations and I
>> do not have any leaking going on.
>
> do you also call coUninitialize after ending the work? it could have
> something to do, as an update usually always comes after a retrieval
>
>
> --
> Best regards :)
>
> Guillem Vicens Meier
> Dep. Informatica Green Service S.A.
> www.clubgreenoasis.com
> --
> Contribute to the Indy Docs project: http://docs.indyproject.org
> --
> In order to contact me remove the -nospam
>
.
- References:
- Getting OLE Error 800A0E7F
- From: Bert Moorthaemer
- Re: Getting OLE Error 800A0E7F
- From: Guillem
- Getting OLE Error 800A0E7F
- Prev by Date: Re: Checking for pending updates of ADO Dataset
- Next by Date: Re: Checking for pending updates of ADO Dataset
- Previous by thread: Re: Getting OLE Error 800A0E7F
- Next by thread: SQL Server 2005: Cannot refresh a TADOTable
- Index(es):
Relevant Pages
|
