Re: UPDATE SQL for Excel - very slow - any suggestions?
- From: "Martin B" <mb@xxxxxx>
- Date: Tue, 24 Jan 2006 14:03:03 +0100
I just tried that.
It is too slow, and I also need to create columns that may be missing in the
input table.
I am using a memory table instead.
By the way, doesn't the ADODataSet use UPDATE SQL in the background?
"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
news:vr3bt1d4m8dhqgvvb7q9994o01ogdut62g@xxxxxxxxxx
>
>>Hello world,
>>
>>I am using ADO components to connect to a datasource; the user can
>>connect to Excel sheets, Access or any other database.
>>
>>After using the program, the user will want to update certain fields in
>>the
>>datasource.
>>I have implemented this with standard "UPDATE" SQL queries.
>>This works fine with Access. But with Excel sheets it is very slow (factor
>>60).
>>This is probably due to the fact that there is no index in the key fields
>>in
>>Excel.
>>
>>Any suggestions?
>
> Don't use SQL
> Use a TadoDataset set the commandType to cmdTableDirect
> commandText to the data*** you want to edit
> Then make all your changes directly to the tadoDataset
> --
> Brian Bushay (TeamB)
> Bbushay@xxxxxxxxx
.
- Follow-Ups:
- Re: UPDATE SQL for Excel - very slow - any suggestions?
- From: Brian Bushay TeamB
- Re: UPDATE SQL for Excel - very slow - any suggestions?
- References:
- UPDATE SQL for Excel - very slow - any suggestions?
- From: Martin B
- Re: UPDATE SQL for Excel - very slow - any suggestions?
- From: Brian Bushay TeamB
- UPDATE SQL for Excel - very slow - any suggestions?
- Prev by Date: Re: RefreshRecord
- Next by Date: master detail with ADO recordsets
- Previous by thread: Re: UPDATE SQL for Excel - very slow - any suggestions?
- Next by thread: Re: UPDATE SQL for Excel - very slow - any suggestions?
- Index(es):