Results 1 to 8 of 8
  1. #1
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Louisville, Kentucky, USA
    Posts
    605
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Date() (2000 v 2003)

    Hello Everyone....

    I'm having problems with DATE(). The db is/was programmed in Access 2000, but 1 of the users of the db is using 2003 and bombs everywhere DATE() is in code and in the vb window DATE() is hightlighted. No one else who's working in the db and has Access 2000 gets the error. I've verified there aren't any missing/broken references.

    Does anyone have any ideas as to what might be causing this problem.

    p.s. The db can't be created/designed in 2003 as the IT folks are just getting around to upgrading the office and at this time only upper mgmt have the upgrade.

    Thanks for any suggestions.
    Roberta Price <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Date() (2000 v 2003)

    It sounds suspiciously like a references problem, but you've already checked for that. What does the error message for the Access 2003 user say?

  3. #3
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Date() (2000 v 2003)

    The Microsoft Office 12.0 Object Library looks out of place - that's from Office 2007!

    Try the following on your machine with Office 2000:
    - Select Debug | Compile <project>.
    - If you get error messages, you'll have to take care of them before continuing with the next step.
    - Clear the last ticked check box in Tools | References and click OK
    - Select Debug | Compile <project>.
    - If you get errors about object not being recognized, add the reference back, otherwise leave it cleared.
    - Repeat with the next-to-last reference, etc. until you've tried all of them except the first two (which you cannot clear).
    As a result, you'll have a database with only the essential references.
    See if this version works on the PC with Office 2003.

  4. #4
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Louisville, Kentucky, USA
    Posts
    605
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Date() (2000 v 2003)

    Edited by HansV to replace Word doc with the picture it contained - saves the reader a few clicks

    Something along the line of "...doesn't recognize this object...". It's happening on a manager's computer who has 2003 and is out of the office until later today. I can't replicate the issue because no one else has 2003 and no one else is getting the error message. Once she returns I will reproduce the error and give an update.

    With that said, attached are the references that are in the 2000 db. If any of them look incorrect, please let me know.
    Roberta Price <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

  5. #5
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Louisville, Kentucky, USA
    Posts
    605
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Date() (2000 v 2003)

    Thanks Hans for the suggestions. I believe I was able to resolve the problem and is as follows:

    On the machine with 2000, the reference to Microsoft Object 12.0 is selected and doesn't have the 11.0 library at all to select.
    On the machine with 2003, the reference to Microsoft Object 11.0 is selected (with a Missing Reference for 12.0) but doesn't have 12.0 library at all to select.

    IT is baffled as well. She verified that each machine has the same service packs for the respective version (excluding 2003). She needs to leave (Access) 2000 on the new machines because so many db's are created in 2000. She seems to think it's a conflict with versioning. I disagree....2000 has a newer Library than 2003 but doesn't have the older Library and 2003 has an older Library and doesn't have the newer library. My assumption is it's a service pack issue....but can't argue with IT.

    I can't understand why 2000 would have Library 12 and not 11 and why 2003 would have Library 11 and not 12.

    Ahhhh...another mystery to solve.

    Again thanks.
    Roberta Price <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Date() (2000 v 2003)

    Just to clarify:
    Office 9.0 = Office 2000
    Office 10.0 = Office XP (aka 2002)
    Office 11.0 = Office 2003
    Office 12.0 = Office 2007

    Was anything related to Office 2007 installed on the PC with Office 2000, for example the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 file formats? This lets users with an older version of Office open documents that use the new XML-based file format of Office 2007. That would explain the presence of the Microsoft Office 12.0 Object Library - it is *not* the library for Office 2000!

  7. #7
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Louisville, Kentucky, USA
    Posts
    605
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Date() (2000 v 2003)

    IT says no...and I believe them, as I stated earlier, we are just now upgrading to 2003 by the time we get to anything related to 2007, there will be 2 new versions. LOL!

    According to IT, the service packs are all the same on each machine. However, she did inform me that the analysts were getting new machines tomorrow (over the weekend). So problem might be resolved.

    I do however, have another question, if I could (without creating a new post).

    I have a field (short time), I can enter 23:59 (23 minutes:59 seconds) but can't enter 24:01(24 minutes:1 second). Why? I've even changed the formating to : nn:ss, still no luck!!
    Roberta Price <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

  8. #8
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Date() (2000 v 2003)

    Access (or rather Windows) interprets 23:59 as 23 hours 59 minutes. Since we have a 24 hour day, 24:01 is not possible. You must prefix the time with 0: to indicate that you mean minutes and seconds, e.g. 0:23:59 and 0:24:01.

    Note: the nn:ss format only affects the way the times are displayed, not how they are entered.

Posting Permissions

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