Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 941739 - Last Review: August 2, 2011 - Revision: 5.0
Error message when you use the Import Wizard in Microsoft Forecaster: “Invalid delimiter specifiedâ€
Source:
Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
You select a file to import with the Import Wizard. You receive the following error message:
Invalid Delimiter Specified
You cannot continue with the import. This error appears in all imports: Capital, Human Resources, Line Items and Account Balances.
- This error occurs because the user has selected the Excel spreadsheet file that has a .xls or .xlsx file name extension instead of the tab-delimited text file for the import. See Resolution 1 in the "Resolution" section.
- The error occurs because more fields have been mapped than what is defined in the import file. See Resolution 2 in the "Resolution" section.
Resolution 1
The import file must be a text file that has fixed length or tab-delimited columns. To do this, follow these steps:
- Open Excel, create the import file, and then click Save.
- Format all cells as Text.
- Save the file again as a text file that has a .txt extension.
- Within the import wizard, the user can click the Back button to return to the screen where the import file is selected. The user will reselect the new text file and continue.
Resolution 2
Verify that each field has been mapped to a column in the import file. For example, your import file contains 11 columns of data. However, the import wizard has 12 columns mapped.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALSâ€) FOR ANY PURPOSE.
THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Microsoft Forecaster 7.0
- Microsoft Dynamics GP 10.0
- Microsoft Dynamics GP 9.0
- Microsoft Business Solutions–Great Plains 8.0
- Microsoft Dynamics SL 7.0
- Microsoft Dynamics SL 6.5
- Microsoft Business Solutions–Solomon 6.0
- Microsoft Dynamics AX 4.0
- Microsoft Dynamics AX 3.0
- Microsoft Dynamics NAV 5.0
- Microsoft Dynamics NAV 4.0
- Microsoft Business Solutions–Navision 3.70, when used with:
| kbmbsmigrate kberrmsg kbnomt kbtshoot KB941739 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate