🚀 go-pugleaf

I'm currently using SQL statements to perform that transfer of data as they
are far quicker than inserting() and posting() using ADO, but I was just
seeing if their were any quicker ways of transferring data within Access
rather than extracting a record at a time within database1 and transfering
it into the same table within database2 as a new record.

it would be great if i could get all the field data for a single field
within a table and bulk copy that across, then move to the  next field
within the same table and do the same, this way I could discard of the
fields that are no longer relevent or available within the next database.


"YangKai Liu" <yangkai.liu@burkelee.com> wrote in message
news:40027217@newsgroups.borland.com...
> Is there anything preventing you from using SQL statement to perform the
> operation? If not, just use TADOQuery or TADOCommand as the vehicle to
send
> the SQL statement to your DBMS, then it's done.
>
>
> "Daniel Stevenson" <d.stevenson@ocreage.com.au> �b�l��
> news:400222b2@newsgroups.borland.com �����g...
> > I'm currently looking into alternate (and hopefully faster) ways of
moving
> > data from one database to another where the field names are the same in
> each
> > table and in some situations where some fields are not present within
the
> > new database.
> >
> > The original database has tables that are related to one another (ie.
are
> in
> > master/detail relationship) and therefore data integrity needs to be
> > maintained
> >
> > I currently move one record across to the new database at a time, then
> check
> > all other tables for records that are related to the master record and
> copy
> > those across before incrementing the master record, therefore keeping
all
> > the records in their correct relationship.
> > I'm finding this method very slow especially with a database holding
over
> > 50,000 records.
> >
> > I was wondering if there was a bulk method of copying data or an SQL
> method
> > that might be faster.
> >
> > I'm currently using BCB6 with ADO and an Access database.
> >
> > Thanks
> >
> >
>
>