We are using a previously-reliable generic sub to read db tables.
The SQLOpen command now returns -1 because the db connection is lost.
All our VB is unchanged and still valid. The problem must be due to ODBC connection properties.
Cannot debug as we have limited admin rights to tools config.
Any suggestions how to check the properties of our ODBC connection to see if it's fallen over?
If you simple want to check the ODBC properties, navigate to the ODBC Data Sources applet in Control Panel > Administrative Tools.
Create a new DSN there by specifying the values known to you and test.
If you are using SQLOpen you can also set the prompt parameter to display the driver dialog.
But as Sachin eludes, perhaps you've moved PC's and did not create the ODBC on that machine.
If you do not want to be burdoned with DSN problems you can go DSN-less. Here's a link indicating how to format your connection strings to help you out. http://www.able-consulting.com/MDAC/...BC_DSNLess.htm