Query Fails in WinXP using Access 2003

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dank06
    New Member
    • Apr 2008
    • 2

    Query Fails in WinXP using Access 2003

    We recently upgraded a '97 Access db to Access 2003. The user interface is programmed in VB6.4
    When the user attempts to query the data from a Win2k environment, the data is available.
    When the user attempts the query from a WinXP environment, the data does not appear at all.

    Any suggestions to solve this problem?

    --dank06
    Last edited by dank06; Apr 24 '08, 07:53 PM. Reason: Detail addition/title refine
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32663

    #2
    Unfortunately, there is much more involved than simply the operating system environment.

    I suggest you Google for published differences when migrating from Access 97 upwards. You'll probably need to check out the SQL you're using with this to see if anything is likely to fall foul of the newer rules.

    Comment

    • puppydogbuddy
      Recognized Expert Top Contributor
      • May 2007
      • 1923

      #3
      Many of the conversion problems with Access 2003 relate to Microsoft implementing the sandbox mode as the default mode beginning with Access/Office 2003. Under the sandbox mode, macros and other expressions were evaluated as unsafe expressions for security reasons, and therefore, disabled. See the first link for detailed information on the sandbox mode. See the second link for info on new bugs introduced with Access 2003.




      List of new bugs in Microsoft Access 2003 introduced by Service Pack 3 for Office 2003.

      Comment

      • missinglinq
        Recognized Expert Specialist
        • Nov 2006
        • 3533

        #4
        Actually, Allen Browne also has a page on upgrading from v97 to v2000 and beyond:

        Issues you may face when converting a Microsoft Access 97 database to a later version. Covers setup issues, conversion issue, and usability issues.


        Welcome to bytes!

        Linq ;0)>

        Comment

        • dank06
          New Member
          • Apr 2008
          • 2

          #5
          Ok, thanks for all your help! My suspicion is that it's a sandbox issue and some unsafe vb code.
          I will post back if I have any problems
          Thanks again

          Comment

          • NeoPa
            Recognized Expert Moderator MVP
            • Oct 2006
            • 32663

            #6
            Please do Dan :)

            We like to know how you get on.

            Comment

            Working...