I have a VB2010 application that is connecting to a Microsoft Jet SQL back end that is installed on PCs with Access 2003 loaded. Presumably the installation of Access 2003 also registers the machine with Microsoft.Jet.OLEDB.4.0.
We are starting to transition users over to Office 2007 (even though virtually none of them actually use Access.) But apparently this transition has messed up the ability to access the old Access MDB, because when the first user tried to log into my app, they got a message:
The Microsoft.Jet.OLEDB.4.0 provider is not registered on the local machine.
Do I have to create a new application for the 2007 machines with a new connection string? Or is there something else that will allow machines with EITHER Access 2003 or Access 2007 to access the mdb on the server?