Post reply

ODBC Problem with Access 2007

  • November 5, 2007 at 1:39 am

    #76811

    hi everyone,

    I have an Access 2003 application using ODBC connection to access my data tables in Microsoft SQL 2005. My problem occurred when I upgraded to access 2007.

    I converted my application to Access 2007 version. After this conversion my username and password are no more validated. the application is telling me invalid username and password as if my ODBCs are not working anymore.

    However if I configure my ODBCs from my Administrative tools they are connecting properly with the same username and password.

    I would appreciate any help in this subject.

    Thank You

  • November 6, 2007 at 12:35 am

    #748533

    hi,

    when ever you uppgrade your versions., it remove all your previous login informations.

    you need to again create DSN and provoide and selct your upgrad

    control in administrative tool.

    remain things setups as usal of 2000 configuration.

    just you need again generate new DSN.

    Kindest Regards,

    madhusudhanreddy
    myspace.com

  • November 6, 2007 at 7:49 am

    #748671

    If you haven't already, you will need to apply SQL Server 2005 Service Pack 2 to your SQL Server instance.

    SQL Server Service Pack 2 adds "awareness" for Office 2007 (Office 12) products and may solve your problem.

    Regards,

    "Key"
    MCITP: DBA, MCSE, MCTS: SQL 2005, OCP

  • November 6, 2007 at 9:22 am

    #748741

    Thank you all for your quick response

    I will try first to download the SP2 for SQL 2005 as suggested by Mr Wilson and see if it solves the problem because the DSN configuration was not affected by the conversion since my application reads the information from registry and they are read correctly.

    However, during my debug today I noticed that the problem occurs when I reach the statement: set gConSQL = CreateWorkspace("", gSQLLogin, gSQLPwd, dbUseODBC) the workspace is kept empty. According to Microsoft Office 2007 help dbUseODBC will generate runtime error and they suggest to change the connection to ADO instead of DAO when reading external data .

    This is what I want to avoid if possible because it will require lots of changes in my code.

    thanks again for your help and as i said i hope the SP2 will solve the issue although i am not very optimistic about the results.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply