Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Modifying an import specification

0 views
Skip to first unread message

wmdm...@att.net

unread,
Feb 2, 2008, 10:22:23 AM2/2/08
to
I need to modify an existing text import specification by adding several
additional columns to the 15 that are currently in the spec. The import
wizard allows me to add the columns, choose save, and choose to overwrite
the existing specification. However, the new columns are not saved.

I also opened the system table msysIMEXColumns which contains the columns
for each specification, but it does not allow a manual add of additional
columns.

I would appreciate any thoughts on why additional columns can't be added.

Bill


wmdmurphy

unread,
Feb 2, 2008, 12:06:39 PM2/2/08
to
I found Microsoft article 271798 that has a workaround for this problem
which exists in Access 2000 but was fixed in Access 2002, see below:

SYMPTOMS
When you import or you export a text file, and you use a previously created
import or export specification, if you make changes to the specification (by
adding or by removing fields, for example) your changes are silently
discarded and the original specification remains intact.
Back to the top

RESOLUTION
When you make a change to the specification, click OK instead of Save As, in
the Import Specification or the Export Specification dialog box. Continue
through the wizard, and when you click Finish, Access prompts you to save
changes to the specification. Click Yes and the changes persist.

NOTE: If you are working with a fixed width text file, you must make changes
to the number of fields and the field size from the Import Text Wizard or
the Export Text Wizard instead of the Import Specification or the Export
Specification dialog box. You can save the changes to the specification when
you click Finish at the end of the wizard.
Back to the top

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.

This problem was corrected in Microsoft Access 2002.

<wmdm...@att.net> wrote in message
news:PU%oj.5650$0o7...@newssvr13.news.prodigy.net...

uparrow.gif
0 new messages