Recent content by viegasp

  1. V

    Problem with ODBC.

    Just to clarify the issue regarding the trusted connection, when i choose the OBDC entry a SQL Server login box is show and i've an option (check box) to select the trusted connection or in alternative two text boxes (Login Id and Password) to use SQL auth, what i said is that no mather what...
  2. V

    Problem with ODBC.

    no it's not new and also no new configurations were made in the computer. the connectivity with the server exists of course. i can query the databases using a pass-through with DNS specified and i also can log in into sql server management studio or any other query tool.
  3. V

    Problem with ODBC.

    yes it does. and the strange thing is that i connect to other sql servers 2000, 2005 and 2008 using the same odbc drivers and i have no problems at all. the inverse is already true, other people in my network connect sucessfully to this specific server using the same drivers and the same MS...
  4. V

    Problem with ODBC.

    Yes the button is still disabled. No mather what option i use (win auth or sql auth - the server allows both ) the button remains disabled. I have the following drivers: SQL Native Client - SQLNCLI.dll SQL Server - SQLSRV32.dll Other users can sucessfully connect using the same version...
  5. V

    Problem with ODBC.

    Yes i am admin and i can create new ODBC's. I already try to re-create the DSN and test the connection sucessfully. But the OK button in the login box remais disabled. :confused:
  6. V

    Problem with ODBC.

    The thing is that i can't create the table because the OK button in the login dialog remains disabled... no errors occur before the login box is show. But if i use the following DNS in a pass-through query i can sucessfully query the database ODBC;DSN=«ServerName»;DATABASE=«DatabaseName»...
  7. V

    Problem with ODBC.

    Hi all, In MS Access 2010 trial version when i try to link a table using ODBC the SQL Server login box appears with the OK button disabled. This issue happens only in a specific 2005 SQL server. Other users in my network can sucessfully connect to that SQL server so i'm assuming that this...
Back
Top Bottom