C
Cherilyn
I currently have an automated process that I use a import
specification to import a text file. I created the import
spec after I had XP loaded. The import specification is
currently working great, however, I needed to update the
import specification and now it will no longer import my
file unless I save it as unicode first. The original spec
appears to have been created with a default page code and
has a 0 in the file type of MSysIMEXSpecs table and the
new spec now forces that I pick a code page in which I
chose unicode and it makes the MSysIMEXSpecs file type
1200. I have tried all the page code types and none are
0. Has anyone else had this type of problem? Do you know
how to set the file type in the MSysIMEXSpecs to 0? I
need to get this automated without an operator having to
open the file and save as unicode each time. Thanks in
advance to anyone who can help.
specification to import a text file. I created the import
spec after I had XP loaded. The import specification is
currently working great, however, I needed to update the
import specification and now it will no longer import my
file unless I save it as unicode first. The original spec
appears to have been created with a default page code and
has a 0 in the file type of MSysIMEXSpecs table and the
new spec now forces that I pick a code page in which I
chose unicode and it makes the MSysIMEXSpecs file type
1200. I have tried all the page code types and none are
0. Has anyone else had this type of problem? Do you know
how to set the file type in the MSysIMEXSpecs to 0? I
need to get this automated without an operator having to
open the file and save as unicode each time. Thanks in
advance to anyone who can help.