-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken Access Converter #29
Comments
@JohnShelley are you able to install this official release of Microsoft Access runtime? https://www.microsoft.com/en-us/download/details.aspx?id=13255 |
@JohnShelley this problem is occurring because I think that you have the click-to-run version of Microsoft Office installed. There are lots of different flavours of Microsoft Office some of which are installed in different locations on your system and registered differently. There are several methods for confirming if you have the "click-to-run" version of Microsoft Office. Click-to-run isn't actually a full installation of office. In reality it goes and gets a fresh copy of the relevant office applications each time you launch one of them. i.e. you don't really have Access on your system as a regular installed piece of software even though it appears in your start menu. All the documentation that I can find online suggest that the solution is to install a copy of the Microsoft Access Runtime. This is an official, free version of the core components of Microsoft Access. It should include all the components necessary to allow the database converter to run. https://www.microsoft.com/en-us/download/details.aspx?id=13255 |
Closing this issue because JShelley has confirmed that installing the Access runtime makes the first message go away. I have created a separate issue (#33) to address the second error message about "code 6" errors. |
JS: The converter from the old Access format to the new SQL format is not working. We've tried it on two machines and received two errors. Microsoft Access works fine on both machines.
PB: I suspect that this is due to a flavour of Microsoft Access that is installed. There are many and they install in weird places sometimes.
The text was updated successfully, but these errors were encountered: