Importing a file with odd extension in XP

  • Thread starter Thread starter Trish
  • Start date Start date
T

Trish

We have a database that was programed to import data from
a text file. The users would need to change the .txt to
another extension (that wasn't really an extension) such
as .CI for storage and organization purposes. In 97 they
were still able to import this file even if it had the .CI
extension. However, we now have XP and this will no
longer work. They receive an error message telling them
there was an error with the import. We have tracked it
down to XP not accepting any files with an extension it
does not know. Does anyone have any ideas how to fix
this. We tried to tell the person using this program to
just change the file back to .txt and that was not
acceptable. We need to find a fix that she will not have
to do anything on her end.

Any help would be greatly appreciated. Thanks, in advance.
Trish
 
Hi Trish,

Here are two different approaches.

This http://support.microsoft.com/default.aspx?scid=kb;en-us;304206
shows how to change the extensions that Access will accept. The neatest
method is the last, editing the registry (provided you're careful<g>).

This http://support.microsoft.com/default.aspx?scid=kb;EN-GB;306144
includes code that automatically makes a copy of the textfile with a
..txt extension and imports that.On Tue, 29 Jul 2003 05:38:33 -0700,

Trish said:
We have a database that was programed to import data from
a text file. The users would need to change the .txt to
another extension (that wasn't really an extension) such
as .CI for storage and organization purposes. In 97 they
were still able to import this file even if it had the .CI
extension. However, we now have XP and this will no
longer work. They receive an error message telling them
there was an error with the import. We have tracked it
down to XP not accepting any files with an extension it
does not know. Does anyone have any ideas how to fix
this. We tried to tell the person using this program to
just change the file back to .txt and that was not
acceptable. We need to find a fix that she will not have
to do anything on her end.

Any help would be greatly appreciated. Thanks, in advance.
Trish

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
 
Back
Top