🚀 go-pugleaf

For Access (but not for most other DBMS) try to use TADOTable with
CursorLocation = crServer. Using transaction (open transaction, insert 5000
or 19000 rows, then commit transaction, then start new transation etc.) will
also speed up inserts (again, for other DBMS this may or may be not true).
For best results you may look at third-party components, but they may
require more code.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"Dan" <Dan@do.not.spam> ???????/???????? ? ???????? ?????????: 
news:46645ac3@newsgroups.borland.com...
> Hi Folks,
>
> I need some help. I have some tables that I want to move to Access.  But 
> moving the data from one format to the other seems to take FOREVER with my 
> code.
>
> For simplicity, the source is basically two tables, a source table which 
> contains header information and forms the basis of a link to the 12 
> records in a subtable.  The sub table is basically a memo field containing 
> table-link information that, each of which has 3 fields, containing 520 
> records.  The new target format I am moving to basically breaks out that 
> memo into 520 unique records in each of three tables.
>
> As you could see, to import one complete record from the source, I would 
> have to add the following number of records to the target:
>
> 1 Header Record
> And then 12x representing each expanded subtable:
>   520 (1st field) records
>   520 (2nd field) records
>   520 (3rd field) records
>
> This is ends up being 6240+6240+6240+1 = 18,721 records!
>
> Oh, why the new format?? why???  Seriously though, there are reasons for 
> it!  For starters, the 1st and 2nd fields are the same in each 12 
> sub-tables, so I can get away with only adding them once.  Then, there are 
> a number of mathematical operations I would like to easily perform on the 
> data, that can be performed via SQL, that it is another bonus; there are 
> more.
>
> So, performing 19K Insert statements, like I said, TAKES FOREVER.
> What is the best way to do this besides the following pseudo:
>   TADOQuery *Query;
>   Query->SQL->Text = "INSERT ONE RECORD SQL STATEMENT"
>   Quey->ExecSQL();
>
> and then looping thru 19k more times?
>
>
> Thanks in advance!
>
> Dan