Import Specification will not save

[Guest]

I have an import specification with 31 fields for a fixed-length ASCII text
file. I have attempted to add two more fields (increasing the record length
to 411 characters), but upon attempting to use or to save the modified import
spec, the added fields disappear from the fields list.

Opening MSysIMEXColumns and trying to change the import spec directly gives
the error message "This dataset is not updateable"

How can I add fields to an import spec? (I did add the appropriate fields
to the table into which I am importing, spelled and sized correctly)

Thanks

Larry Schuller

 

[Jeff Boyce]

Larry

Where did you "attempt to add two more fields"?

Have you tried starting over, importing the "new" ASCII file and specifying
the field lengths in a new definition?

 

[Guest]

Jeff,

Thanks for trying to answer my question. Writing a whole new spec from
scratch is not acceptable, not with my typographical error rate.

To answer your question: I tried adding the fields during the import
process. That is, Alt-File, Get External Data, Import File, Text File, Fixed
Length Fields, Click on "Advanced" Button, Click on "Specs" Button, Open a
previously saved Specification, Go to the bottom of the list of specs, add a
field (just as if I was writing a new spec, field by field). Here is where I
encounter my problem.

Clicking the "Save As" button deletes the newly added fields before saving.
It does save, however. I know this because I can change field names and they
are retained. I can delete fields, too. But when I try to add even the same
fields back on, I cannot. Opening the system table (MSysIMEXColumns) where
the specs are stored did not work either, as the tables cannot accept direct
input of changes.

After researching several places, I found this discussion group and found
some similar questions (none of which answered my question), so started this
thread.

Before posting this question here, I posted the same question in another
thread (Editing an Import Specification) which, afterward, I could not find
again. So started this thread. Since then, I found the prior thread and an
answer from Joe Fallon. It seems the "MSysIMEXColumns" table can accept
changes if they are passed through a select query.

I have not had time to verify the solution as 100% effective yet, but have
high hopes.

 

[John Nurick]

Hi Larry,

IIRC this problem has occurred in at least one recent version of Access
and was fixed by an Office service pac. If you're using Office 2003,
install SP1 or SP2; if an earlier version, make sure the most recent
service packs are installed.