Results 1 to 4 of 4
  1. #1
    Star Lounger
    Join Date
    Mar 2003
    Location
    Summerville, South Carolina, USA
    Posts
    66
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Jet Engine Issue (Access 2000)

    I have been getting an error message on an Access database for the last couple of weeks. First, the message is "The Microsoft Jet database engine could not find the object 'Scripts'. Make sure the object exists and that you spell its name and the path name correctly."

    The database is a front-end access and back-end Oracle via an ODBC Connection. The database sets on a shared network drive. Also, I don't have a table or object named script. And this error message only appears at random times.

    Any help would be great. Thanks.

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

    Re: Jet Engine Issue (Access 2000)

    Scripts is the internal name Access uses for macros. Perhaps your frontend has become slightly corrupt. First see if a Compact and Repair causes an error message. You could also try to import all database objects from the frontend into a new blank database. You will have to set the startup options anew, as well as non-standard references in the Visual Basic Editor (if you have them.) See if the new frontend works without problems.

  3. #3
    Star Lounger
    Join Date
    Mar 2003
    Location
    Summerville, South Carolina, USA
    Posts
    66
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Jet Engine Issue (Access 2000)

    Would it be fair to say that if I move all (or most) of my macros to VB, that I would have less problems? I did not create this database and the ones I do create are 99% VBA and don't use macros. I don't have issues with those. I am in the process of changing everything to VBA.

    Would that be correct?

    Thanks.

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

    Re: Jet Engine Issue (Access 2000)

    I myself hardly use macros (only an AutoKeys macro occasionally), because macros are hard to maintain and lack error handling, but in itself there is no reason why macros shouldn't function correctly, so I can't guarantee that converting the macros to VBA will help. It won't harm, though.

Posting Permissions

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