Over the past few days, some readers have encountered odbc error code in Microsoft Excel 97-2003. This problem can arise for several reasons. We’ll cover them below.

Hopefully user can export contacts to Excel from one shared folder. The following message should appear:

“Microsoft Excel 97-2003 Translator encountered ODBC error while opening file while creating field mapping. [ODBC
[microsoft] Driver Manager] No data source name purchased and no default driver specified. Problem “

No, for direct export to * .pst data record or * .csv file. Plus, there is no problem exporting your own notifications to Excel.

I found a regularly reported problem on the world wide web, but did not find a solution. Anyone see how to fix the problem? Or are users using a dedicated workaround (* .csv)?

I am facing the following problem: A user wants to export contacts from their boss’s public folder to Excel, but receives an error message:

“Microsoft Excel 97-2003 Translator encountered an ODBC error on opening that you simply submit to create a mapping for a specific field. [ODBC
[microsoft] Driver Manager] No data source store found and the default switch It is not specified. “

Export to * .pst or * .csv file is working. Exporting your contacts to Excel files is not a problem either.
The problem is often described on the Internet, but I have not found a solution. Do you know the solution? Or is it not worth negotiating with export to * .csv?


  • You are trying to open a mail merge document in Microsoft Word 2010, Word 2013, or Word 2016.
  • The data in the document is a Microsoft Excel spreadsheet (* .xlsx) that is of course stored in a shared folder.
  • The document is already open.

An error occurred: the portal does not have the largest store format.


If you save the XLSX music file to a shared folder and create a mail merge as a data source in Word, Word will only open part of the XLSX file. If a web user tries to open a Word document that uses the same data at the same time, only read-only permissions may be granted, and therefore the need will fail.


an odbc error has occurred in the microsoft excel 97-2003

To work around this issue, useUse this .csv or .xls file as specific source data instead of a complex .xlsx file. For example, open your marketing information source in Excel and then cut costs in an Excel 97-2003 workbook (* .XLS) or comma delimited file (* .CSV).

  • 2 minutes to read.
  • Applies to:
    Word with Office 365, Word 2019, Word 2013, Word 2016, Word 2010

Office 365 ProPlus will be renamed Microsoft and then 365 Apps for Enterprise. You can find other important information about this reading change in this article .

When trying to import a comma separated values ​​(.csv) file in Outlook 2010 or Outlook 2013, the following error occurs:

File error in comma separated translator when initializing translator to possibly create a field map.

Outlook was able to receive data as file . Make sure the file is correct, that you have permission to open itand that the other program didn’t find it.

The characters used to represent line feeds are called the record separator string.

Some Mac or Unix systems can symbolize line feeds using the single line feed (LF) control mechanism. Other systems may use completely alternative linefeed control characters.

In Power BI Desktop, the early Access databases and Excel workbook versions (.XLS files in Excel 97-2003 form) use the Access database engine concurrently. There are three common professions that can interfere with the correct operation of the Access Database Engine.

Situation 1: The Database Access Mechanism Is Not Installed

If most of the Power BI Desktop error messages mean that the DBA is not implemented, then you need to install the 32-bit or 64-bit version of the DBA, which is your version of Power BI Desktop. You can install the Access Database Engine by loading the page .

If you are working with feeds yes While buying a gateway to connect your most important data, you need to install the Access Database Engine on the computer connecting the gateway.

Situation 2: The Bit Version Of Access Database Engine (32-bit Or 64-bit) Must Be Different From Your Bit Version Of Power BI Desktop

This situation often occurs when our installed version of Microsoft Office is actually 32-bit, and the installed version of Power BI Desktop is 64-bit. The opposite can also happen, and after that it is quite possible that the binary version does not match. You can also complete these solutions to resolve the incompatibility of other applications that might work with other 32-bit COM applications as these SSDTs are Visual Studio. If you do use a Microsoft 365 subscription, you will know Situation for 3 point and a different resolution. Any of the solutions used can fix this version mismatch error:

Solution 1

Change your Power BI Desktop version to match this binary version of your Microsoft Office installation.

  1. To change the bit value For BI power Desktop, uninstall BI power Desktop and install the version of BI Energy Source Desktop that matches your Office installation.

  2. To select Power BI Desktop version a, select More download options on the Power BI Desktop checkout page.

  3. On the download page that opens, select your language and click the “Download” button.

  4. On the screen that appears, check the box next to PBIDesktop.msi for 32-bit or PBIDesktop_x64.msi for 64-bit.

    In the following screenshot, the 64-bit version is selected.


    If you are using the 32-bit version of Power BI Desktop when building very large data models, you might run out of memory issues.

Solution 2

Change the bit version of Microsoft Office to match the bit version associated with your Power BI Desktop installation:

  1. Remove Microsoft Office

  2. Install the version of Office that matches your Power BI Desktop installation.

Solution 3

an odbc error has occurred in the microsoft excel 97-2003

If an error occurs while trying to open the .XLS directory. (an .Excel .97-2003 .classeur), .you. same tyanaya bank. avoid .Access .Database .Engine .by. Open the ..XLS file in Excel and save it as an XLSX file.

Solution 4

If the previous four solutions don’t work, you can install both versions of Access the Database Engine. However, this recommended workaround is not. While installing both fixes this issue for Power Query for Excel and Power BI Desktop, it will cause errors and therefore issues for any application that specifically (by default) uses the binary version of most databases. The Access Engine data is used first. were installed first.

To set both bit versions in the Access Database Engine, follow these steps:

  1. Install the two binaries of the Access Database Engine from the download page .

  2. Start any version of the Access Engine database using the light / passive switch. For example:

      c:  users  joe  downloads  AccessDatabaseEngine.exe / passivec:  users  joe  downloads  AccessDatabaseEngine_x64.exe / passive 

Situation 3: Problems Or Access To .XLS Files With A Microsoft Subscription

When you purchase a Microsoft 365 365 subscription, be it Office 2013 or Office 2016, the core providerand Access is stored in a virtual registry that Microsoft Office processes can access. Therefore, the mashup plugin (which is responsible for running Excel Power and BI Desktop, is not an Office 365 and is not an Office process) cannot be implemented by the Access Database Engine Provider.

To avoid this situation, download and install these Database Engine Redistributables that struggle with the bit version of your Power BI Desktop installation. For more information on bit versions, see the previous sections of this article.

Other Situations May Cause Problems With The Import

We try to solve as many problems as possible that may arise with Access or XLS files. If you encounter an issue that is definitely not covered in this article, please submit a specific issue question to Power BI Support . We regularly check for available issues that may affect a large number of customers, and add relevant articles.

  • 3 minutes to read.

If the bit version of the Access database engine isIt differs from the bit version of Microsoft Office installed, Office applications will not be able to use the Access database engine.

If your organization is using 32-bit Power BI Desktop when building full-size models, you may experience data issues due to insufficient memory.