none
Visual Studio 2019 connection to Access 2019 64 bit RRS feed

  • Question

  • I cannot get VS 2019 to connect to Access 2019 64 bit. I get the error of The "Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.

    I have downloaded and installed the ACE provider and it shows up on the VS Data Source connection wizard, as does JET.  I select ACE, but get the above error when I test the connection.

    Any suggestions would be appreciated.  I've had many MVPs give me suggestions, but they only work on prior versions of VS, or on 32 bit Access. 

    Using JET, I can connect to .mdb Access databases, but that won't do what I need. 

    Thanks,

    Dave

    Tuesday, October 15, 2019 7:47 PM

All replies

  • Hi,

    About the issue, maybe you can refer to the thread "Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine".

    Regards,

    Kyle


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, October 16, 2019 1:46 AM
    Moderator
  • I already did that before this post.  It doesn't even come close to answering the question since it relates to software scenarios that aren't my problem and with software that isn't Visual Studio 2019 trying to connect with Access 2019 - 64 bit.  VS 2019 changed something.  I've gone to my 2018 VS and can connect.  However, since I'm to be teaching VS 2019 and Access 2019 - 64 bit connection to University students starting in January, I have to have a solution for that exact connection, which no one seems to have an answer for, including Microsoft.  Of course, Microsoft won't even let me talk to them or their support, so I use the forums and get the same run-around that doesn't address the issue.  Then some moderator decides, and I quote, "the issue is too severe so we aren't going to address it".

    If someone will address the EXACT issue I would be very grateful.

    Thank you!

    Wednesday, October 16, 2019 2:13 AM
  • Hi scenicaz,

    If this problem only occurs in Visual Studio 2019, I suggest you submit a issue to the Developer Community. Specific steps refer to the link Report a problem.

    Regards,

    Kyle


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, October 16, 2019 2:38 AM
    Moderator
  • I've already done that.  Nothing except an automated e-mail that says it's being "triaged", whatever that's supposed to mean.  Then a month later another automated e-mail that says that since there was no activity on this issue it's being deleted or inactivated and no further action will be taken.

    That's a lot of non-help from a company that used to be very responsive to its customers.  

    So there's no way to actually talk with someone with knowledge of VS 2019 to get some help?

    I'll submit again, anyway.  I need this resolved so I can teach it to just under 300 students this next semester.  That's a lot of need.



    • Edited by scenicaz Wednesday, October 16, 2019 1:50 PM
    Wednesday, October 16, 2019 1:45 PM
  • I have exactly the same problem - I have recently had to update to Visual Studio 2019 and a system that was working fine previously now has this error. I have spent a long time trying to research the issue and followed exactly what you have done but with similar lack of success. Have you had any responses since October?

    All the best.

    Tuesday, January 28, 2020 3:25 PM
  • I have had ZERO replies except the message that says it’s too complicated for them to do anything with, and that there aren’t enough other questions on this subject to justify spending any time on it.  The only reason no one else looks at it is because they are blocked from doing so, so we have to post once, then again, and I’ve counted over 25 separate messages about this problem, but not on any one post, just one at a time.

     

    Microsoft isn’t taking care of its own software issues.

    Another developer posted this same issue last week also.  You saw the responses I get.  I started posting on this issue over a year ago, the response was the same.  So I tried again in October.  My clients are now talking about scrapping Microsoft for anything and going to Apple.  I know MS doesn't care about just 20 clients and 2,000 individual users, but I do.

    There is a thread posted on UtterAccess.com by Raas that shows the problems.  The thread is lengthy and at times convoluted, but there was limited success getting some data to pull up in message boxes.  However, even with following the suggestions and code given, VS still won't connect controls to .accdb, just message boxes, and that doesn't do a thing for me.  Even MVPs for MS can't get it to work.  

    Everyone seems to agree that MS needs to step up and correct the problem, and quickly.  Do a 64 bit version that talks to .accdb, or an engine that connects 32 bit to 64 bit.

    I have contacted text book authors that usually can get help from their contacts in MS.  They won't even write new texts on the subject of VB, VS, and accdb.  I talked with McGraw-Hill, Cengage, Prentice, Wrox, and O'Reilly publishers, and they have no plans to bring out anything new on the subject of 2019 until this issue is resolved, and they have no clue when, or if, that will be.

    IT'S UP TO MICROSOFT to save their own product now.

    Tuesday, January 28, 2020 4:03 PM
  • Hello, 

    >Do a 64 bit version that talks to .accdb, or an engine that connects 32 bit to 64 bit.

    As far as I remember Visual Studio 2019 remain 32 bit application.

    So, you would not be able to use any of 64 bit DLL's with Studio (not with application you developed, but with Studio it self).

    If you need to use something from Studio you must have 32 bit version of what ever it is. 


    Sincerely, Highly skilled coding monkey.

    Tuesday, January 28, 2020 4:16 PM
  • And that, is, pardon me, but absolutely ridiculous!  Why have a 64 bit version for better and faster throughput and processing, but can't use it?  Having to revert to 32 bit is going backwards in technology, not forward.

    So, this does NOT answer the question or address the problem.  

    "Do a 64 bit version that talks to .accdb, or an engine that connects 32 bit to 64 bit."  I'd do a 64 bit version if VS made a 64 bit product!!!!   Also, there isn't an engine that connects 32 bit to 64 bit!!!!

    Wednesday, January 29, 2020 3:39 AM
  • >absolutely ridiculous!

    You have an opportunity to provide 64-bit Development Studio.

    This could give you option to be a second Bill Gaits.

    Use it for good before someone do this...


    Sincerely, Highly skilled coding monkey.

    Wednesday, January 29, 2020 11:01 AM