Facebook
Google
GitHub
Linkedin
this is resoved now but made me spend nearly two hours digging for solution, trying things and restarting.
i was just about to say forget the whole thing and load it into a VM when i got it working. so i decided may as well post it here rather, maybe search engines will index this and help others in same position. maybe someone could find it faster, i don't use it that often and was frustrated with bunch of suggestions that seem to be just copies of each other.
Problem was that software on an older target machine (also was used as development station) needed changes.
So to make some changes more comfortably using my personal computer i temporarily installed same vintage VS here (an Express edition) so i would not need to worry about switching back. my machine is running Win10 64bit, with 64-bit office (and happens to have Access installed too)
but when i tried to open access DB it would crap out with the:
"The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine."
As a workaround i created sample DB and saved it in an older format (2003 Access, *.mdb) which tested ok.
and of course connection provider had to be replaced from "Microsoft.ACE.OLEDB.12.0" to "Microsoft.Jet.OLEDB.4.0"
that did the trick but older file is so retro, few neat features that exist now were missing in older file format.
if this is to get facelift, it need to be all 64-bit, so i needed to make it work using ACCDB database...
most success stories mentioned installing Access runtimes but this was a hit and miss. others suggested removing Office and loading 32-bit everything (yeah right...). besides, if anything i would like to make things all run in 64-bit.
it sure looked like 32/64 bit compatibility and VS project was set to target x86 but i did not see way to change it to x64 (did not have access to target machine at a time).
the actual fix for me was:
1. in VS2010Express enable Build Configuration Manager using menu:
Tools>Options>Projects and Solutions>General>Show advanced build configurations (why would this be deactived?)
2. while there also change editor settings to show line numbers (why would something important like this be deactivead by default?)
3. then using menu Build, one can reach Configuration Manager and add x64 (hmm...not impressed, using ADD still seem to replace previous choice).
after this, one could load project and change actual project properties (project properties, Compile, Platform, Active and Debug switch to x64), then add build output path. not sure why would this get cleared, i doubt anyone in 2010 (and certainly MS developer) was tryong to develop for windows using monitor set to 640x480.
actually this looks rather nice and snappy. it is just that some of default settings are kinda burried and need some manual intervention to get things setup.
i was just about to say forget the whole thing and load it into a VM when i got it working. so i decided may as well post it here rather, maybe search engines will index this and help others in same position. maybe someone could find it faster, i don't use it that often and was frustrated with bunch of suggestions that seem to be just copies of each other.
Problem was that software on an older target machine (also was used as development station) needed changes.
So to make some changes more comfortably using my personal computer i temporarily installed same vintage VS here (an Express edition) so i would not need to worry about switching back. my machine is running Win10 64bit, with 64-bit office (and happens to have Access installed too)
but when i tried to open access DB it would crap out with the:
"The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine."
As a workaround i created sample DB and saved it in an older format (2003 Access, *.mdb) which tested ok.
and of course connection provider had to be replaced from "Microsoft.ACE.OLEDB.12.0" to "Microsoft.Jet.OLEDB.4.0"
that did the trick but older file is so retro, few neat features that exist now were missing in older file format.
if this is to get facelift, it need to be all 64-bit, so i needed to make it work using ACCDB database...
most success stories mentioned installing Access runtimes but this was a hit and miss. others suggested removing Office and loading 32-bit everything (yeah right...). besides, if anything i would like to make things all run in 64-bit.
it sure looked like 32/64 bit compatibility and VS project was set to target x86 but i did not see way to change it to x64 (did not have access to target machine at a time).
the actual fix for me was:
1. in VS2010Express enable Build Configuration Manager using menu:
Tools>Options>Projects and Solutions>General>Show advanced build configurations (why would this be deactived?)
2. while there also change editor settings to show line numbers (why would something important like this be deactivead by default?)
3. then using menu Build, one can reach Configuration Manager and add x64 (hmm...not impressed, using ADD still seem to replace previous choice).
after this, one could load project and change actual project properties (project properties, Compile, Platform, Active and Debug switch to x64), then add build output path. not sure why would this get cleared, i doubt anyone in 2010 (and certainly MS developer) was tryong to develop for windows using monitor set to 640x480.
actually this looks rather nice and snappy. it is just that some of default settings are kinda burried and need some manual intervention to get things setup.
