Hi, Rick.
Import specifications are saved in Jet tables, something that ADP's don't
have. You'll need another method of automatically importing the text files
to the destination table using specific column names, data types and column
sizes. The natural choice is a DTS package, which is far more flexible than
mere import specifications. If you're not familiar with the DTS Designer in
SQL Server, then try creating a schema.ini file for the formatting
information for the import via a SQL query.
For the syntax in your schema.ini file, you'll find the specifications and
information for using text files with Access on these Web pages:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcjetschema_ini_file.asp
http://msdn.microsoft.com/library/d.../en-us/office97/html/workingwithtextfiles.asp
And if you were using an MDB linked to the SQL Server tables instead of an
ADP, Jet could write the schema.ini file for you. (Jet is still pretty
useful for those who aren't using Jet for the back end.) For example usage
of a schema.ini file using a query, please see the following Web page:
http://groups.google.com/group/micr...*+author:camaro&rnum=2&hl=en#e1335a172ce29d27
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.