Results 1 to 9 of 9
  1. #1
    Join Date
    Apr 2008
    Posts
    4

    Unanswered: Expression Works in MA 97 but not 2000

    I have a MA database that has to be updated to MA2000. It works fine in '97 but am being forced to upgrade for other reasons.

    All expressions that include the Date() being compared to a table doesn't seem to work. The following are a couple that give off #Error in 2000 but it displays perfect in '97. Any suggestions, hints would be highly appreciative.

    =Dcount("TicketID", "Paw5","[Date]=Date()")

    =dsum(nz("AmtFin","Paw5","[PicdUp]=2 and [Date]>Date()-60")

  2. #2
    Join Date
    Jan 2005
    Posts
    6
    Check your VBA references. One might be missing. I have seen similar behaviour where basic built-in functions stop working.

  3. #3
    Join Date
    Apr 2008
    Posts
    4
    I'm afraid I don't understand what your telling me to do.

    I created this database program several years back (around 2001 I believe) and haven't needed to do anything since that so I'm very rusty.

    I just assumed it was something that changed with the versions themselves with the syntax.

    I basically put the database on a CD and then pulled it into Microsoft Access 2000 on another computer. So all the table names should be the same (if that's what you mean when you say VBA).

  4. #4
    Join Date
    Jan 2005
    Posts
    6
    Oh, OK
    Open one of your forms in design and view the code.
    Use menu option Tools|References...
    See if any of them say "Missing". If you have the problem you have to browse and locate the file associated with the reference.
    If none of them say "Missing" then you have some other problem but I cannot think what.

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    It could also be a reference to a different version of the same file.

    For example, I've had that same thing happen after making a reference to outlook objects and then moving the database to a computer with a different version of outlook. The reference wasn't missing, but was now referring to the same filename, different version. The Date() and Now() functions stopped working.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Apr 2008
    Posts
    4
    StarTrekker....I believe that is what has happened. It doesn't seem to recognize the Date() function. Wherever that is mentioned it spits out the Error instead of a number. How would one go about correcting that problem? I can't seem to find the Tools--> References as pointed out in a previous post in the 2000 edition of access.

  7. #7
    Join Date
    Apr 2008
    Posts
    4
    The problem ended up being the Kodak Reference Library as suggested earlier. I had to click View --> Code. Then click the Tools --> References. Thanks for the help.

  8. #8
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Glad you got it sorted
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  9. #9
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    Make sure that DAO library is referenced before the ado library in your references and that should fix the problem

    Access 2K included the ado reference as a default which when you then add the dao reference it came second and those functions you described would fail.
    Dale Houston, TX

Posting Permissions

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