Repeatedly import files. Should I use the same file name?

[crobaseball]

Hi, I will be consistently importing new data into my db. But I'd prefer to have the file name to import be different to reflect what data actually gets changed. And just as obviously want to save the import steps so I'm not constantly changing the format of the fields. Is there a way to do this as a saved import?

[June7]

I've never use Saved Import Specification.

Review http://www.accessmvp.com/KDSnell/EXCEL_MainPage.htm

[crobaseball]

Never mind. Under the saved imports, you can click on the file path and change it as needed. Tho certainly handling this as VBA or SQL is prob better

[ItsMe]

... Is there a way to do this as a saved import?

I use saved import procedures for text files. I don't know if there is a new fangled way to save import procedures for .xlsx files. Here is an example for fixed width text. Also, csv is just a text file so I don't think of them as Excel files or worksheets.

 DoCmd.TransferText acImportFixed, "ProcedureName", _
   "tblMyTable", strPath & strFilename

EDIT: Also, you can import your named and saved import procedures from one DB file to another DB file using advanced options via the Wizard.

[CJ_London]

If you create a linked table to a generically named file (.csv, .xlsx, whatever) in a default location - lets say for the purposes of this explanation that name is importdata.csv

1. copy your .xlsx file to a default location and name as importdata.csv (so you still have the original named whatever and wherever)
2. create a linked table to importdata.csv
3. create an append/update query as required to transfer data from the linked table to your db table (could have multiple queries if several tables to be updated)
4. run the query(s)

so next time....
1. repeat step 1 - replacing the existing importdata.csv
2. repeat step 4
...job done