Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 133
  • Last Modified:

Access Database Text Import For Append

When I am importing a text file for appending to an existing Access table I am having problems with the import wanting to define a field as a number when it needs to be text.  As a result I am getting import errors as there is text ultimately showing up in the field.  Why doesn't an Access import for append take on the field properties of the table being appended to?  

What is a better way of importing the data without having to import into a new table each time and then append?  Or, am I approaching this in the wrong way?  Thanks.  - Reilly
0
tomfarrar
Asked:
tomfarrar
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
What is a better way of importing the data without having to import into a new table each time and then append?
Well ... that is the best way - i.e. import into a "staging" table, and then validate that data prior to moving it to your live table. This allows you to catch any data issues before it hits your live tables. You can provide users with a form where they can review data, or correct errors, etc and then use a standard APPEND query to move the data over to live.

If you simply cannot do the staging table, then you'd need to setup an "Import Spec", which allows you to define the characteristics of the incoming fields and such. Capricorn1 shows how to do that here: http://www.experts-exchange.com/Database/MS_Access/Q_28532814.html
0
 
Dale FyeCommented:
You might also consider rather than importing the data, linking to it.  Then, once you have the linked table (which really ends up being your staging table), you would write a query that imports the data into your production table and does the explicit conversions for you, so you might use cstr([fieldName]), to ensure that the field which contains numbers is actually appended as a string.
0
 
tomfarrarAuthor Commented:
Yea, the staging table may end up the solution.  A minor problem it is causing is there are multiple source "text" files (same fields) that would be required to import into the staging table one at a time.  Just trying to eliminate the additional steps.
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
Dale FyeCommented:
As Scott mentioned above, the other advantage of a staging table (either imported or linked) is that you can "validate that data prior to moving it to your live table".  This is the technique that I generally use because you never know when someone has attempted to manipulate the raw text or Excel file.  By using the staging table, you can test for values in one or more fields that may not be valid and can warn the user before importing those records, or could block importing of those records all together.
0
 
tomfarrarAuthor Commented:
Linking might ultimately be the solution as the data are download (.csv) from a data warehouse.  Ideally Access could link directly to the warehouse query results, but that is not going to happen any time soon (I don't think).  So I am working with 5 download files I need to get into an Access table.  That is where I am.
0
 
tomfarrarAuthor Commented:
So, here is the question.  If I use a staging table, do I need to re-create it each time I bring one of the text files in?  Or is there a way to create a staging table (with correct data types or whatever) that would ensure the data comes in correctly each time I import one of the text files?  Thanks.
0
 
PatHartmanCommented:
It is the import spec that is going to control the format of the columns.  Use the TransferText method and specify the import spec.  To create the import spec initially, you need to run the import ONCE manually so you can step through it and define all the data types.  Then press the "Advanced" button to save the spec.  Once it is saved, you can automate the import.

Since you want to reuse one name for the import table, run a delete query before you import the next set of data.  Run any validation against the staging table, then run an append query to the final table.  You can automate everything but handling errors may require user interaction.
0
 
tomfarrarAuthor Commented:
I got the part about the import spec, I think.  But I am not sure of the TransferText method.  Is that some macro command?
0
 
Rey Obrero (Capricorn1)Commented:
the command line is

DoCmd.TransferText acImportDelim, "ImportSpecificationName", "TableName", "C:\folderName\myText.csv" , True

if you have looked at the link posted by Scott, the code is there
0
 
tomfarrarAuthor Commented:
Thanks All - It appears Scott's post had all the answers I needed, and with the additional guidance from the rest of you I was able to get there.
0
 
tomfarrarAuthor Commented:
Think this question's points have been awarded.  Not sure why attention is needed..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now