How to transfer import/export specs into Access 2007 adp project

[PaulB]

I have an Access 97 mdb database that I have converted to Access 2007. I
would like to transfer the import/export specs from this database to my
Access 2007 adp project. When I view the system tables in the adp project, I
do not see the standard MSysIMEXSpecs or MSysIMEXColumn tables (which may be
becuase it's an adp projct), nor are there any existing import/export specs
in the adp project. When I try to import the specs from the mdb database into
the adp project, the option checkbox for import/export specs is grayed (not
available). I can transfer the two MSysIMEX tables, but they are, of course,
not recognized by the adp project as import/export specs. Since I am loath to
redo these complex import specs (over 180 fields in some cases, is there some
way to get these specs into the adp project? Thanks.

 

[Roger Carlson]

Have you tried creating an import spec? I don't have 2007 loaded here, so I
can't check, but in 2003, when I try to import at text file, it doesn't
allow me to create or save a spec.

--
--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

 

[PaulB]

Yes, I just tried to create an import spec in 2007 adp project. I was even
able to copy rows from the old database import spec - but you can't save it -
and thus you can't access in vb code using, for example, TransferText. It
must be because it's an adp project. That's the only thing that I can figure.
It may be that one is required to use SQL Server SSIS.

 

[John Nurick]

I can't check it here either, Roger. But as far as I know the reason
ADPs can't use import/export specs is that the .adp file can't contain
the system tables that store the specs.

One possible approach to the OP's problem would be to write VBA code
that can read a spec from MSysIMEXSpecs and MSysIMEXColumns and write
the equivalent schema.ini.

 

[PaulB]

Thanks, guys. I think that's the answer.

I can't check it here either, Roger. But as far as I know the reason
ADPs can't use import/export specs is that the .adp file can't contain
the system tables that store the specs.

One possible approach to the OP's problem would be to write VBA code
that can read a spec from MSysIMEXSpecs and MSysIMEXColumns and write
the equivalent schema.ini.

 

[Steve_A]

I know this is bit late but what I did was inport a 97 formated database with
the specs in it and they work just fine in 2007 except some that have date
formats.