import/export specifications

[shawn]

Is there a way to automate setting up table import/export
specifications by using an existing MS Access table? Here
is my problem: I have a sample access database that has
about 100 tables. I know have a series of text files with
more up-to-date information in them then the tables that
are already in Access.

I need a method to import the revised text files in the
proper format rather than going in and actual setting up
the field information using the import text wizard. Also,
I will be needing to do this on a regular basis as I get
new files (which wouldn't be a problem if I had import
specifications already set up!)

There is likely an easy way to do this...however, I am
just an amateur. Can someone please offer some
assistance???

thanks!

 

[Roger Carlson]

Not sure what you mean. If you use the wizard to create a specification,
you can save it and use it with the TransferText method of the DoCmd object
to automate the code import.

On the other hand, if you want to use you own import spec rather than the
Access provided ones, you can create your own in a table. I have used this
method on occasion when I needed more control of the process.

On my website (see sig below) is a small sample database called:
"UpdateDirectFixed2k.mdb" which demonstrates this. Look at the code in the
"basUpdateDirectFixedwoSpec" module.

 

[Shawn]

Thanks so much for the reply Roger. Here is my problem
though...I can use the import wizard no problem but I have
a database that needs to import about 5 tables for the
first time. However, I do have another sample database
that was set up that already includes those tables...just
not with the current data in those tables. That sample
database does not have import specs saved anywhere. I was
hoping there was some method to simply use the tables that
are already in the sample database (i.e. use the table
structure) to somehow build import specs.

I am not very savvy with any type of VB code or anything
either! Hopefully you can reply and let me know if
there is anything I can do. In the meantime, I will check
out your site.

thanks!

-----Original Message-----
Not sure what you mean. If you use the wizard to create a specification,
you can save it and use it with the TransferText method of the DoCmd object
to automate the code import.

On the other hand, if you want to use you own import spec rather than the
Access provided ones, you can create your own in a table. I have used this
method on occasion when I needed more control of the process.