Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Gary Costigan
Yak Posting Veteran
95 Posts |
 Posted - 2006-10-12 : 13:12:00
|
| Hi, I work for a large corporation with offices across the U.S.A., and build Excel files that are used to extract and format data coming from my SQL server. Our offices are connected via high speed intranet and earlier this year everyone received new HP computers. After the new PC's arrived I sent out instructions on how to setup the ODBC connection needed to access the SQL data and everything was working fine until recently. The program that I have recently sent out to the field is experiencing connection recognition problems where even thought the ODBC connection is listed in the "USER DSN" menu, the program still wants the user to select the connection by clicking on it, click OK, and then when the Login and Password menu pop up click OK again before it will establish the connection. When we first started experiencing problems we found that if we "Unchecked" the use ANSI boxes the program worked fine again for about a week, but we are now back to square one by getting the problem described above. This has me baffled as I'm not sure if it's a problem with my PC when I'm building the program, an ODBC problem, or server problem. Our IT department is constantly pushing upgrades to our PC's and I'm wondering if it it's an update that has caused the problem. Any time we check the configuration of the ODBC the test comes back as successful. Any help or suggestions would be appreciated. Thanks. GC |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-10-16 : 05:07:11
|
| can you post the connection string you're using?is the change default database option on the dsn checked?--------------------keeping it simple... |
 |
|
|
|
|
|
ODBC Connection Recognition