Access 2010 Connection to Current Database No Longer Working

I have been using the following statement to set an ADODB Connection to the current database thru multiple versions of Access.  However, after upgrading to Access 2010, the statement is no longer working.  It crashes the database.  Can someone help me create a connection to an open, current database?  I've attached my current code.

Set cnnCurrent = Application.CurrentProject.Connection

Thank you.
nquinn94Director of AdministrationAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kanti PrasadCommented:
Your  ACE version seems to be to your Access DB and so ACEOLEDB.DLL path in the registry is not pointing to the corresponding ACE version.

Run a repair on the  access db
nquinn94Director of AdministrationAuthor Commented:
I did try the compact and repair and it did not resolve the problem.  I am starting to believe the issue with with my installation of Access, as I tested the procedure on another computer (using runtime) and it worked fine.  Ever since an installation of Microsoft Project 2013 on my machine, my Access 2010 runs a configuration each and every time I open the program.  (photo attached).  I've read that having multiple version of Microsoft products installed can cause this issue, but I'm not sure how to resolve it.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Multiple versions of Access can certainly cause issues, especially if you're dealing with version prior to 2007 - but it's not clear that you're running multiple versions of Access, and it seems instead you're running a "mixed bag" of Office products (i.e. Project 2013, Access 2010). In general, you'll find life to be much easier if you maintain the same versions of all Office products.

If you must run separate versions, then the way  most of the Access devs have been doing it is to use Virtual Machines. For example, I support applications ranging from Access 97 up through 2013. I'm running 2013 on my "main" desktop, so I have virtual machines to run Access 2010, 2007, 2003, 2002 and 97. When I need to work in those environments, I just fire up the VM and I don't have to worry with the whole "Please wait while Windows configures blah blah".

That said, if you don't want to do this, you'll very likely be faced with an uninstall/reinstall to get things right. You might try a Repair install (just open Control Panel - Programs, and double click on the Access installation, and select Repair). That very likely will not work, however.

Also be certain that your Windows installation is fully up to date.
nquinn94Director of AdministrationAuthor Commented:
I found a registry update that fixed the problem!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nquinn94Director of AdministrationAuthor Commented:
The tips provided by both experts lead me to find the solution on a Microsoft Support site!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.