Re: Speed issue...



Hi!

About 30 fields, number and text. No blobs, no long strings.
It is constantly slow. I am also using CalcFields event and turning
that off speeds things up by 2x when scrolling the database. Instead
of 1 second it takes about 0.5 seconds to move to the next record.

Each scroll operation executes a new Locate call with 2 indexed fields on
a database with about 3000 records.

DataForm.Table.Locate('LoID;CoID', VarArrayOf([DataForm.LTable['ID'],
DataForm.CTable['ID']]),[]);

Thats where the 0.5 second comes from. All tables here are TAdoTable.

The CalcFields fills four Calculated fields with the sum of 3 other number
fields
from the same record. This is the other 0.5 seconds of the .Next call cost.

Making an edit is as slow as I mentioned.

Thanks!
Atmapuri

"Francois Malan" <Francois.Malan.removeThis@xxxxxxxxxxxxxx> wrote in message
news:466fe0c0$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Atmapuri wrote:

Hi!

I am using TAdoTable and when I perform:

Table.Edit;
Table['Field'] := Value;
Table.Post;

This takes about 4-5 seconds on a modern PC. It works,
but it is incredibly slow. Is there a way to handle MS Access
database faster?

Or am I doing something completely silly and this should
not be so slow?

Thanks!
Atmapuri

A little bit more info please.

How many fields in the table definition? Which datatypes? Any long
strings or blobs for example? How many records are returned from your
db query? How are you measuring? Is it constantly 4 seconds or only for
the first edit? How fast is it when you repeat the process?

--



.



Relevant Pages

  • Re: Working with NON-NULL terminated strings
    ... but will be stored in the ADT as a string. ... strings are null terminated. ... will retrieve the BLOBs from the ADT, but I want the BLOBs to be ... Since memcpy() doesn't need to take this ...
    (comp.lang.c)
  • Working with NON-NULL terminated strings
    ... I am retrieving BLOBs from a database into an ADT that is capable of holding strings amongst many other data types. ...
    (comp.lang.c)
  • Re: Working with NON-NULL terminated strings
    ... char array), but will be stored in the ADT as a string. ... strings are null terminated. ... will retrieve the BLOBs from the ADT, but I want the BLOBs to be ... I have to convert the byte stream into a "safe" ...
    (comp.lang.c)
  • Re: Working with NON-NULL terminated strings
    ... char array), but will be stored in the ADT as a string. ... strings are null terminated. ... will retrieve the BLOBs from the ADT, but I want the BLOBs to be ... expect null terminated strings) will continue to "work" (return ...
    (comp.lang.c)