I assume you are using ODBC? If so that is probably the root of the problem. I just assisted someone with a Delphi executable writing to a visual fox table through ODBC. Importing 15000 records was taking 6 to 8 hours. We were able to reduce the time to 12 minutes by putting the data in a Dbase table and creating a VFP executable that opened the table and pushed the data in. I am sure a native Access exe could do the same thing here - woops does anyone actually write access exe programs any more? You could try Scanning the table and scattering to an array and then appending to the table from the array. That should avoid the field naming problem. Another approach might be to close and then reopen the tables at every 1000 records to cause the MDB to flush its buffers. Access really has problems accepting large amounts of data when transaction processing is not on. Hope some of this is useful :).