Results 1 to 6 of 6
  1. #1
    3 Star Lounger
    Join Date
    Mar 2006
    Location
    Pittsburgh, Pennsylvania, USA
    Posts
    289
    Thanks
    0
    Thanked 1 Time in 1 Post

    Import Specifications (2003 sp2)

    Is there a way to import a single text file Import Specification from another database?
    Thanks
    chuck

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Specifications (2003 sp2)

    You can import *all* import/export specifications from another database by selecting File | Get External Data | Import...
    In the dialog that appears, click Options...
    Tick the check box "Import/export specifications" then click OK.

    Importing a single specification is possible, but it's rather tricky since you have to manipulate two normally hidden system tables; I'd avoid that.

  3. #3
    3 Star Lounger
    Join Date
    Mar 2006
    Location
    Pittsburgh, Pennsylvania, USA
    Posts
    289
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Import Specifications (2003 sp2)

    You triggered an idea... I used a make table query based on MSysIMEXSpecs table with the specification I need as criteria and chose my destination database as the target. Safe and sound.
    Thanks
    chuck

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Specifications (2003 sp2)

    Don't forget MSysIMEXColumns then - it contains the column (field) settings for the import/export specifications listed in MSysIMEXSpecs. SpecID is the field linking them.

  5. #5
    3 Star Lounger
    Join Date
    Mar 2006
    Location
    Pittsburgh, Pennsylvania, USA
    Posts
    289
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Import Specifications (2003 sp2)

    Just so I do not lead anyone astray, using a make-table query did not work. The resulting table does not have system-table attributes and therefore is not recognized by the TransferText Method. So I exported the 'definitions only' of each table, MSysIMEXSpecs and MSysIMEXColumns, to the new database and then used append queries to append only the specification and columns I needed.

    Thanks Hans for the heads up on the MSysIMEXColumns table.
    Thanks
    chuck

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Specifications (2003 sp2)

    The system tables always exist, even if you don't have any import/export specifications, and I think they are protected against accidental deletion or overwriting. That's why a make-table query fails to produce the genuine article. But append and delete queries on the existing tables work, as you have found.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •