-->
The pc has Excel 97 and Excel 2000 on it but we verified it sends other data from Access 97 to Excel 2000.
This same report sends to Word 2000 just fine as a rich text file.
Is there another way to export this report into Excel so we can change the data or does anyone know why we would get an Overflow error.
I don't believe they have any service packs installed for Access 97.
I am exporting my data from a Microsoft Access Report to a Excel speardsheet and occasionally i receive an error which just displays 'Overflow'. Feb 26, 2013 I have cleared it by getting all users to exit the application which is linked to tables in a backend database (Access 2010), and then I perform the 'Compact & Repair Database' from within the backend database. I would like to button the application down to where whatever the user(s) are doing. Thanks for responding, Bill. They are not using their.
In Power BI Desktop, both Access databases and early versions of Excel workbooks (.XLS files of type Excel 97-2003) use the Access Database Engine. There are three common situations that can prevent the Access Database Engine from working properly.
Situation 1: No Access Database Engine is installed
If the Power BI Desktop error message indicates the Access Database Engine isn't installed, you must install the Access Database Engine version, either 32-bit or 64-bit, that matches your Power BI Desktop version. You can install the Access Database Engine from the downloads page.
Note
If the installed Access Database Engine bit-version is different from your Microsoft Office installation's bit-version, Office applications won't be able to use the Access Database Engine.
Situation 2: The Access Database Engine bit-version (32-bit or 64-bit) is different from your Power BI Desktop bit-version
This situation often occurs when the installed version of Microsoft Office is 32-bit, and the version of Power BI Desktop installed is 64-bit. The opposite can occur as well and the bit-version mismatch will occur in either case. If you're using an Office 365 subscription, see Situation 3 for a different issue and resolution. Any of the following solutions can remedy this bit-version mismatch error:
Solution 1
Change the version of Power BI Desktop to match the bit-version of your Microsoft Office installation.
- To change the bit-version of Power BI Desktop, uninstall Power BI Desktop, and then install the version of Power BI Desktop that matches your Office installation.
- To select a version of Power BI Desktop, select Advanced download options on the Power BI Desktop download page.
- On the download page that appears, choose your language and then select the Download button.
- On the screen that appears, select the checkbox beside PBIDesktop.msi for the 32-bit version, or PBIDesktop_x64.msi for the 64-bit version.In the following screen shot, the 64-bit version is selected.NoteIf you use the 32-bit version of Power BI Desktop when creating very large data models, you might experience out-of-memory issues.
Solution 2
Change the bit-version of Microsoft Office to match the bit-version of your Power BI Desktop installation:
- Uninstall Microsoft Office
- Install the version of Office that matches your Power BI Desktop installation.
Solution 3
If the error occurs when you attempt to open an .XLS file (an Excel 97-2003 workbook), you can avoid using the Access Database Engine by opening the .XLS file in Excel, and saving it as an XLSX file.
Solution 4
If the previous three solutions are not feasible, it's possible to install both versions of the Access Database Engine. However, this workaround isn't recommended. Although installing both versions will resolve this issue for Power Query for Excel and Power BI Desktop, it will introduce errors and issues for any application that automatically (by default) uses the bit-version of the Access Database Engine that was installed first.
To install both bit-versions of the Access Database Engine, follow these steps:
- Install both bit-versions of the Access Database Engine from the download page.
- Run each version of the Access Database Engine by using the /passive switch. For example:
Situation 3: Trouble using Access or .XLS files with an Office 365 subscription
If you're using an Office 365 subscription, whether Office 2013 or Office 2016, the Access Database Engine provider is registered in a virtual registry location that's only accessible to Microsoft Office processes. As a result, the Mashup Engine (which is responsible for running non-Office 365 Excel and Power BI Desktop, and isn't an Office process), can't use the Access Database Engine provider.
To remedy this situation, download and install the Access Database Engine redistributable that matches the bit-version of your Power BI Desktop installation. For more information about bit-versions, see the earlier sections in this article.
Other situations that can cause import issues
We strive to cover as many issues that occur with Access or .XLS files as possible. If you encounter an issue that isn't covered in this article, submit a question about the issue to Power BI Support. We regularly look at issues that may be affecting many customers, and include them in our articles.
I have an Access 97 database. There is a report that we would like to send to Excel 2000. When we click the 'Office Links' icon to send the report to Excel, we get a box that says Overflow.The pc has Excel 97 and Excel 2000 on it but we verified it sends other data from Access 97 to Excel 2000.
This same report sends to Word 2000 just fine as a rich text file.
Is there another way to export this report into Excel so we can change the data or does anyone know why we would get an Overflow error.
I don't believe they have any service packs installed for Access 97.