J
John
The situation is in an A2007 mde (a former A2003 db that retained the
mde for some users still have Office 2003) db with sql server 2005
backend. It is a dsn / odbc connection. There are 2 new machines
that now have Windows 7 on them. During a process that has been used
for many years with very little change has now begun to give
intermittent errors. In trying to transfer a part from point A to
point B an error can occur. But, it can happen in which some time
passes (mins or several hrs) and go to transfer the same part and the
transfer will be successful. The error is;
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified.
The non-W7 machines do not have any problems transferring. My initial
thougth is the DSN but how can that be checked? What about the
registry and DSN? The code will construct the DSN if it detects that
the proper DSN is not present. Which is what has occurred for many
years without a problem.
Does anyone have any thoughts on this or have a similar issue?
Thanks
John
mde for some users still have Office 2003) db with sql server 2005
backend. It is a dsn / odbc connection. There are 2 new machines
that now have Windows 7 on them. During a process that has been used
for many years with very little change has now begun to give
intermittent errors. In trying to transfer a part from point A to
point B an error can occur. But, it can happen in which some time
passes (mins or several hrs) and go to transfer the same part and the
transfer will be successful. The error is;
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified.
The non-W7 machines do not have any problems transferring. My initial
thougth is the DSN but how can that be checked? What about the
registry and DSN? The code will construct the DSN if it detects that
the proper DSN is not present. Which is what has occurred for many
years without a problem.
Does anyone have any thoughts on this or have a similar issue?
Thanks
John