Home > Net >  Unable to connect to a 32-bit access2017 winform access2016 (the blog the oledata.mso 16.0.11629.202
Unable to connect to a 32-bit access2017 winform access2016 (the blog the oledata.mso 16.0.11629.202

Time:10-13

The first thing to note, I am a fan of programming, visio studio2017 develop software for the unit, my computer is a 64 - bit operating system, use office software package is office 2016,
I last year has developed a dynamic network is developed for asp.net, use access2016 (the blog the oledata.mso 16.0.11629.20238) (32) as a dynamic website database,, after all, is a network using the database request is not high, when the development has been an error, and prompt the erroneous, but I find a solution through baidu, is to give the computer installed AccessDatabaseEngine, and configured IIS can normal visit, after
Today I again winform software is developed, and also use access2016 (the blog the oledata.mso 16.0.11629.20238) (32-bit) as winform database, this error again prompt "not registered on the local computer 'Microsoft. ACE. The OLEDB. 12.0" provider ", so I search on the Internet again, asp.net are given solution (download and install AccessDatabaseEngine, but when installation tip had already installed can only be repaired, so I have no choice to repair), no winform solution, so I want to install AccessDatabaseEngine_64. Exe software to solve this problem, the system has an error that I have installed the 32-bit office products, cannot install AccessDatabaseEngine_64. Exe software,
What do I do now, I'm desperate!!! Please know the truth of god for help to solve this problem, thank you!

CodePudding user response:

After days of exploration, I finally found the answer, that is at the time of debugging, the anyCPU modification for x86 and then can run normally, (select configuration manager, then platform there is a new button, select new x86 mode)
But there is a strange phenomenon, that is to use x86 mode to compile the runtime DLL cannot use of some third party, it is strange, because I in vs2008 before (32-bit system) can run normally, and is in vs2017 x64 mode also does not have an error, but is in x86 mode is not! Then I use the project - management NuGet to normal after download the DLL,
(PS: this question is very difficult? So many days, or a lover on my own to solve the problem, I am speechless)

CodePudding user response:

reference 1st floor fjptwwm2 response:
after days of exploration, I finally found the answer, that is at the time of debugging, the anyCPU modification for x86 and then can run normally, (select configuration manager, then platform there is a new button, select new x86 mode)
But there is a strange phenomenon, that is to use x86 mode to compile the runtime DLL cannot use of some third party, it is strange, because I in vs2008 before (32-bit system) can run normally, and is in vs2017 x64 mode also does not have an error, but is in x86 mode is not! Then I use the project - management NuGet to normal after download the DLL,
(PS: this question is very difficult? So many days, or a lover on my own to solve the problem, I am speechless)


Because you are not a system programming backgrounds, like me, is this kind of problem, can't, if programming is so easy to solve, not everyone can be programmed
  •  Tags:  
  • C#
  • Related