I got a question today from somewhere I used to work and was unable to answer it.
The project over there is a VB front-end, SQL Server back-end. When reports were needed, the company decided to call into Access 97 and using pass-through queries to call stored procedures as the source, open up reports as needed via a controlling VB form.
The VB front-end uses ADO with OLEDB. Access uses DSN-less connections for the connection string in the reports (for the pass-through query).
They are wondering (and now me) if there would be any harm in changing the connection string in VB to be the DSN-less version. They are looking at doing this so that they only have to maintain one version of the connection string instead of 2.
So, really I have 2 questions:
1) Is it possible to use OLEDB for the connection string in Access 97? (So far it looks like it is not possible)
2) What are the issues with moving from an OLEDB connection string to a DSN-less (ODBC) connection string?