Csv import: direct link vs temp table dump

T

The Dude

Hi guys!

I have to import several "librairies" from csv files.

Hence I have created routines that will import the csv file to a Temp table
then append or delete/append the data to a Final table (with or without
filtering).

My question is to know if that's the best method? Considering that the Temp
table makes a ghost size expand of the Back-end after each import/delete...
that I would no have with a csv direct link. I imagine I could directly
append the filtered data from the csv direct link as well.

(Of course I compact the BE every week...)

Any womments welcome ;)
Thanks
T_D
 
R

Roger Carlson

Personally, I would link the CSV. For one thing, if you do this on a
continuing basis, you only have to over-write the existing CSV files
(assuming the file layout remains the same) and the new data will
automatically show up in the linked tables.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Import lots of CSV 4
help creating a button to import .csv file... and more.. 1
Import errors importing Text into existing table, header vs no hea 3
error importing a .csv file to a linked-table 2
Error Saving Import/Export Spec 1
Temp DBs 2
Linking several CSV files to one table 1
Import new data and replace old data in Access table. 2

Top