Missing Import Capability

[Bob Hannah]

After doing a full install of Office XP, the ability to
import fixed length records in txt format is missing. All
other formats is missing too except ODBC. Uninstalling
and reinstalling does not correct the problem. After
going through the registry I discovered that there were
some major errors there that did not correct with the
install. Also turning off the recovery ability and
replacing the MStext40.dll did not correct this problem.
All patches and hotfixes were applied with out correcting
this problem. Following the corrections for repairing
this problem from the knowledge base also did not correct
this problem. Any help would be appreciated.

 

[John Nurick]

Hi Bob,

You say "the ability to import fixed length records in txt format is
missing". I infer from this that you have no problem importing delimited
text files: please confirm that this is the case.

Exactly what happens when you try to import a fixed-width file? Have you
scrutinised the files you have tried to import: is there anything
unusual in them?

Do they have non-standard extensions? If so, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;304206 and
http://support.microsoft.com/default.aspx?scid=kb;EN-GB;306144

If there's a schema.ini file in the directory you're importing from,
does it contain a section specifying the layout of the file?

Recent versions of Access are rather fussy about textfile formats. You
must have a CR+LF at the end of each record: Unix- or Mac-style files,
or fixed width files with no record separators, must be converted before
they will import. Also, you can't have CRs or LFs in the data.

 

[Bob Hannah]

The ability ti import any records except through ODBC was
missing. I attempted to use the DNS part which also does
not work. The program DATA sources are missing that allow
you to do this did not install, also, everything is in
place for excel and does work.

-----Original Message-----

Hi Bob,

You say "the ability to import fixed length records in txt format is
missing". I infer from this that you have no problem importing delimited
text files: please confirm that this is the case.

Exactly what happens when you try to import a fixed-width file? Have you
scrutinised the files you have tried to import: is there anything
unusual in them?

Do they have non-standard extensions? If so, see
http://support.microsoft.com/default.aspx?scid=kb;en- us;304206 and
http://support.microsoft.com/default.aspx?scid=kb;EN- GB;306144

If there's a schema.ini file in the directory you're importing from,
does it contain a section specifying the layout of the file?

Recent versions of Access are rather fussy about textfile formats. You
must have a CR+LF at the end of each record: Unix- or Mac- style files,
or fixed width files with no record separators, must be converted before
they will import. Also, you can't have CRs or LFs in the data.

After doing a full install of Office XP, the ability to
import fixed length records in txt format is missing. All
other formats is missing too except ODBC. Uninstalling
and reinstalling does not correct the problem. After
going through the registry I discovered that there were
some major errors there that did not correct with the
install. Also turning off the recovery ability and
replacing the MStext40.dll did not correct this problem.
All patches and hotfixes were applied with out correcting
this problem. Following the corrections for repairing
this problem from the knowledge base also did not correct
this problem. Any help would be appreciated.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[Bob Hannah]

The files that I am attempted to import are downloads from
an AS/400. I have done and install of the XP Office to an
Win98 machine and the install went correct and does work,
but will not install correctly to my XP machine.

-----Original Message-----

Hi Bob,

You say "the ability to import fixed length records in txt format is
missing". I infer from this that you have no problem importing delimited
text files: please confirm that this is the case.

Exactly what happens when you try to import a fixed-width file? Have you
scrutinised the files you have tried to import: is there anything
unusual in them?

Do they have non-standard extensions? If so, see
http://support.microsoft.com/default.aspx?scid=kb;en- us;304206 and
http://support.microsoft.com/default.aspx?scid=kb;EN- GB;306144

If there's a schema.ini file in the directory you're importing from,
does it contain a section specifying the layout of the file?

Recent versions of Access are rather fussy about textfile formats. You
must have a CR+LF at the end of each record: Unix- or Mac- style files,
or fixed width files with no record separators, must be converted before
they will import. Also, you can't have CRs or LFs in the data.

After doing a full install of Office XP, the ability to
import fixed length records in txt format is missing. All
other formats is missing too except ODBC. Uninstalling
and reinstalling does not correct the problem. After
going through the registry I discovered that there were
some major errors there that did not correct with the
install. Also turning off the recovery ability and
replacing the MStext40.dll did not correct this problem.
All patches and hotfixes were applied with out correcting
this problem. Following the corrections for repairing
this problem from the knowledge base also did not correct
this problem. Any help would be appreciated.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[John Nurick]

The usual cure is to re-register the relevant DLLs:

If the import/export wizards don't work at all, re-register ACCWIZ.DLL

If it's one or more file formats that aren't listed, re-register the
following files
msexcl40.dll (Excel)
msxbse40.dll (dBase)
mspdox40.dll (Paradox)
mstext40.dll (Text, CSV, tab-delimited))
In Access 97, the filenames contain 35 instead of 40.

To re-register a DLL file,

1) Locate it (usually all these are in the Windows\System32 or
WINNT\System32 folder.

2) Locate the file regsvr32.exe.

3) Drag the DLL file's icon onto the regsvr32.exe icon.

These problems are discussed in the following MS Knowledgebase articles
among others:
http://support.microsoft.com/?id=292269
http://support.microsoft.com/?id=155666
http://support.microsoft.com/?id=171955
or for Access 2002
http://support.microsoft.com/?Id=283881

The ability ti import any records except through ODBC was
missing. I attempted to use the DNS part which also does
not work. The program DATA sources are missing that allow
you to do this did not install, also, everything is in
place for excel and does work.

-----Original Message-----

Hi Bob,

You say "the ability to import fixed length records in txt format is
missing". I infer from this that you have no problem importing delimited
text files: please confirm that this is the case.

Exactly what happens when you try to import a fixed-width file? Have you
scrutinised the files you have tried to import: is there anything
unusual in them?

Do they have non-standard extensions? If so, see
http://support.microsoft.com/default.aspx?scid=kb;en- us;304206 and
http://support.microsoft.com/default.aspx?scid=kb;EN- GB;306144

If there's a schema.ini file in the directory you're importing from,
does it contain a section specifying the layout of the file?

Recent versions of Access are rather fussy about textfile formats. You
must have a CR+LF at the end of each record: Unix- or Mac- style files,
or fixed width files with no record separators, must be converted before
they will import. Also, you can't have CRs or LFs in the data.

After doing a full install of Office XP, the ability to
import fixed length records in txt format is missing. All
other formats is missing too except ODBC. Uninstalling
and reinstalling does not correct the problem. After
going through the registry I discovered that there were
some major errors there that did not correct with the
install. Also turning off the recovery ability and
replacing the MStext40.dll did not correct this problem.
All patches and hotfixes were applied with out correcting
this problem. Following the corrections for repairing
this problem from the knowledge base also did not correct
this problem. Any help would be appreciated.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.