ACC: Importing Fixed-Width Text with Embedded Carriage ReturnsLast reviewed: May 12, 1997Article ID: Q153373 |
The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills. When you import or link to a fixed-width text file with fields that contain an embedded carriage-return and line feed control character (ASCII decimal values 13 and 10 respectively), Microsoft Access interpret this character set as being the end of a record. The remaining portion of the record that follows the CR/LF is considered the beginning of a new record.
CAUSEThe Import Wizard does not evaluate the field with the embedded or "soft" return as part of the field's value.
RESOLUTIONTo work around this behavior, create a custom import specification using Schema.ini and then link to the text file using Visual Basic for Applications. Once linked, you can use a make-table or append query to import the linked data. For more information about using Schema.ini, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q149090 TITLE : ACC: How to Use Schema.ini for Accessing Text Data MORE INFORMATIONThe Microsoft Access Text Import Wizard assumes that a combination of CR/LF designates a new record when parsing a fixed-width formatted text file. Imported or linked data appears in an unexpected format when a field value contains an embedded CR/LF. Using Visual Basic for Applications and the TransferText AcImportFixed generates the same behavior when linking or importing. Using an export/import specification does not override the wizard.
Steps to Reproduce Behavior
REFERENCESFor more information about importing fixed-width text files, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q94107 TITLE: ACC1: How to Import Fixed-Width Text FilesFor more information about accessing data in a text file, search in the Help Index for "accessing text files," or ask the Microsoft Access 97 Office Assistant.
|
Additional query words: truncates missing
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |