My issue with the Ace engine is that there's a 64 bit and 32 bit that are separate & they made it so you can't have both installed at the same time, which the end result is that any applications you or I write we have to make a choice, set your app to compile for 32 bit only or 64 bit only and if the end user has the "other" one installed, well, they're out of luck unless they want to deal with figuring out how to get the other bit-version of Office installed. Office 2013 requires a Windows format & clean install, I figured that out the hard way some 5 or 6 years ago, maybe Office 2016 doesn't have that problem though most people I know still has Office 2010 & some installed 2013 side-by-side with 2010.
Even though I don't do anything with Access databases anymore, as of VS2013 and Office 2013 I still prefer to use the Jet engine and the Access database is the 2003 format (file name ends in .mdb) because the Jet engine is 32bit only (no 64bit available, no confusion) and you simply have to set your program to compile to 32 Bit only which still lets your program to run on 64bit machines. And yes Office 2013 allows you to make/change Access 2003 databases still, I would venture a guess that Office 2016 does too.
Currently using: VS 2010 Ultimate on Win7 Ultimate x64.