Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2004
    Location
    Dallas, TX
    Posts
    6

    Unanswered: Access 2002 Pass-Through Queries w/SQL Server 2000

    I am working on an Access application that uses SQL Server 2000 as the database and Access 2002 as the front end. When this application was in Access 2000, there were no problems. However, now when I go to open any pass-through report (with a stored procedure as the data source) in design mode, it takes forever to open, if it opens. Sometimes it just hang there for 20+ minutes then dies.

    I have read about putting in my WHERE clause in the close event of the report something like WHERE 2=1.

    I have tried opening the reports in Access 2000 and was able to open any of them in design mode with no problems at all.

    In the instance where Access 2000 is installed, it is installed on Windows 98. The occurance of Access 2002 is running on Windows XP.

    I have a few questions.

    1) Is the problem from the version change in Access, or in the operating system change?
    2) Is there any other way to fix this other than adding code to the Close event of the report?

    Jon

  2. #2
    Join Date
    Aug 2004
    Location
    Dallas, TX
    Posts
    6
    Update:

    I just took off Office 2002 on the Windows XP machine and installed Office 2000. I am still having problems opening up any reports that are pass-through queries.

    It looks like the problem may be related to Windows XP, since I had no problems opening the same reports in Office 2002 running on Windows 98.

    Has any else run into this problem? I basically cannot get any work done, since all the reports I need to change are pass-through queries with stored procedures as the data source.

    Any help would be greatly needed.

    I am about to install Office 2003 and try it, but am thinking that it won't work since I am starting to believe that the problem is with Windows XP.

    HELP!

  3. #3
    Join Date
    Aug 2004
    Location
    Dallas, TX
    Posts
    6
    Another Update:

    I compared the ODBC settings on the 2 machines. The Windows 98 machine (the one that was not having any problems) was using SQL Server authentication in its ODBC setting. The Windows XP machine was using Windows NT authentication. I changed the Windows XP machine to use SQL Server authentication and now I can open up the reports normally (except it now asks me for a login and password, which i have to enter 3-4 times then it opens the report). I can make my changes, then when I hit save, it asks me for the login and password 3-4 times again, then returns me to the report menu.

    Once I go back into the report, the change has been made.

    Does the user have to have their ODBC setting as SQL Server Authentication?? They currently are using Windows NT authentication and they can run the application just fine.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •