But I still don’t fully understand the root of the problem. I also found this article: Accessing Excel files on a 圆4 machine, which seems to be related. The first of course is the ADODB drivers involved (a real change between v2003 and v2007) and another between the MMC utilities (Microsoft Management Console–different between x32 and 圆4, with the default being the system you are on – not the application you are trying to control). Microsoft Access Database Engine 2016 Redistributable Though, in SSMS, I can see 2 providers. When prompted, choose one of the following files based on your Windows OS and TNTmips installation architecture:ccessDatabaseEngine4. The issue of moving data-linking between versions can get interesting on a couple of levels. Microsoft access database engine 2019 redistributable 64 bit. If you know more about this, please leave a comment below so we can better understand the problem!įellow Visio MVP Al Edlund tried to shed some light on the subject for me, but it was a bit over my head: Do default installs of 64-bit Windows 7 and 64-bit Office & Visio 2010 work just fine regarding data-linking, and I had somehow gummed up my system? Do Microsoft’s default installs really overlook this problem and leave you with non-functioning Visio-Excel communication? I really don’t know where the weak link is. The new engine allowed Visio to extract data from Excel files. Thereafter, I was able to open the Excel file in the External Data window and link data to my shapes: At any rate, I figured there must be something new.Īnd there appears to be! The trick was to install the brand-spanking-new Microsoft Access Database Engine 2010 Redistributable: I know that data drivers or data providers allow all these apps to communicate with each other, but I don’t really know–or care–about details. I poked around a little bit, then thought about the word “Provider” in the expanded error message. Maybe plain English to some of you, but Greek to me! Solution? Download and Install Something! Well, we just saw that it most certainly IS an Excel file, so that didn’t make any sense!Įxpanding the error expanded showed a bit more info: “Error 800a0e7a: Provider cannot be found. I browsed to the Excel file expecting all to go smoothly, when POW! I got this error message: “The selected file is not a Microsoft Excel file or is currently inaccessible.” I opened Visio’s External Data Window, clicked Link Data to Shapes, which started the Data Selector wizard. I started with a very simple Excel 2010 file that had just a few equipment items with their associated list of ports: When I tested on a Virtual PC running 32-Bit Windows 7 Ultimate, and 32-bit Office/Visio 2010, the data-linking worked fine. The “64-bit-ness” seemed to be part of the problem. My Lenovo ThinkPad T410 runs Windows 7 Professional 64-bit, and I have Visio Premium 2010 64-bit installed as well. If you are running 64-bit versions of Windows and Microsoft Office, you might run into the same problem.įortunately, the solution was quite easy! Hi Alan Bourke, I try to made a test on my side.Ive downloaded the 32-bit version of the component above but when I try to install it fails because apparently I have a 64-bit Office. The PC has Office 365 ProPlus and all Office applications are 32-bit and 2016. I ran into a problem linking Visio shapes to Excel data the other day. Im trying to install the Microsoft Access Database Engine 2016 Redistributable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |