Tisky,
I did without success.
Then I took it a step further with a complete OS re-installation prior to installing Office 365 - same result.
I have found many other posts here and on external forums about folks who have installed Office365 and are experiencing similar OBDC issues. Would lead me to believe that Office365 is probably a bad choice for anyone who requires ODBC connectivity.
To elaborate on my re-installation and results:
- Install clean 64bit OS
- Install 32bit Office365
- Attempt to use SysWow64\odbcad32.exe to create or modify a SYSTEM or USER DSN .. FAILS stating driver missing (no .accdb drivers are listed)
- Attempt to install the 32bit Microsoft Database Engine Redistributable .. FAILS stating both 32 and 64bit Office applications exist (can't understand this as the only software on the system was created via Microsoft installation routines for the OS and
Office365)
I have 2 Access ODBC instances that are currently inoperable that are used extensively within our facility, one that contains a lot of VB that would be a major effort to recreate in a different application.
What else can I do to resolve this?