Access 2010 Import Inconsistentcy

[aziska]

Good morning folks,

I have a question regarding an import of a file. I'm attempting to import a text file to a previously constructed table (used as a datashell) with 3 fields that contain leading zeros. If i import the text file as a new table and define the fields as text, the leading zeros are kept and no issues. However, if i attempt to import the text files into the datashell, which has the appropriate fields defined as text fields, the leading zeros are lost and it seems to import them as numbers first. Does anyone know what causes this and how to correct it w/o having to import as a new table everytime. (Can be done, but is more involved process at the moment.)

Thank you very much for your help in advance,

Regards,

Aaron

 

[Joe4]

Are you using an Import Specification?
If so, there may be a problem with it, and you may need to just rebuild it.

 

[aziska]

I am not using the import specification tool yet. I was planning on building one after i get this to work properly. but at the moment i'm just doing the import manually and after i get it to append properly to the datashell, then i will save the import spec. Thanks for the quick reply and for helping me out.

-Aaron

 

[Joe4]

I would recommend importing it once in to a "new table", and before you click "Finish" on the Import Wizard, click on the Advanced tab and save your Import Specification.

Then, try importing into your "datashell" table, but before you click Finish, click on the Advanced tab and bring up the Import Specification, then Finish the import.

What happens then? Do the leading zeroes appear?
If so, you have successfully created the Import Specification you need and will want to use.

 

[aziska]

To the best of my knowledge it looks like the new way of loading using the import spec is working. Thank you very much for your time and patience. Best to you and yours,

-Aaron

 

[Joe4]

Great! Glad to hear it!

Occassionally, I have problems with Import Specs if something in the table has changed, or if I am importing and exporting to the same layout, and try to use the Export Spec to build my Import Specs In almost all instances, simply re-building the Import Spec solved the problem.