Running macros in Access 2007 Runtime on Vista

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jackbenimble999@gmail.com

    Running macros in Access 2007 Runtime on Vista

    Hello!

    Has anyone had trouble running macros on the Access runtime version on
    Vista? I tried enabling macros in the trust center, and thought for
    sure this would solve the problem! But, alas, my hopes were in vain -
    I still get the 2950 error when the Autoexec macro runs. I don't think
    it's a trust folder issue because I'm set the registry key of the app
    path in the install wizard, and the program doesn't give the warning
    message when I run it. The install works perfect on XP!

    many thanks!
    Jack. B. Nimble
  • Salad

    #2
    Re: Running macros in Access 2007 Runtime on Vista

    jackbenimble999 @gmail.com wrote:
    Hello!
    >
    Has anyone had trouble running macros on the Access runtime version on
    Vista? I tried enabling macros in the trust center, and thought for
    sure this would solve the problem! But, alas, my hopes were in vain -
    I still get the 2950 error when the Autoexec macro runs. I don't think
    it's a trust folder issue because I'm set the registry key of the app
    path in the install wizard, and the program doesn't give the warning
    message when I run it. The install works perfect on XP!
    >
    many thanks!
    Jack. B. Nimble
    What is error 2950? I forgot to memorize the trappable error list for
    the test.

    Carve

    Comment

    • lyle fairfield

      #3
      Re: Running macros in Access 2007 Runtime on Vista

      jackbenimble999 @gmail.com wrote in news:f4531a1a-5c58-4235-8068-
      d11b451999fc@y5 g2000hsf.google groups.com:
      This question relates to anyone who has an come across a problem
      running macros on Access 2007 on Vista - particularly on the runtime!
      Any thoughts on this welcome indeed!
      How about guesses? Mine is that your install utility has erred in naming
      some directories and that security prevents running code from non-trusted
      directories and that would include directories that don't exist or are
      inaccessible. The directory system in VISTA seems markedly different from
      that of XP; if your install utility is not up-to-date then it may not take
      this into account.
      If my guess is correct, and I think it has at least one chance in a million
      of being correct, a solution might be to update your install utility and
      VISTA and XP and Office to their latest Service Packs and Updates on all
      machines involved.
      But it's just a guess.
      My other guess would be that you are doing something so incredibly bizarre
      that we can't guess what it is.
      Maybe the first guess is preferable?

      Comment

      • Salad

        #4
        Re: Running macros in Access 2007 Runtime on Vista

        lyle fairfield wrote:
        jackbenimble999 @gmail.com wrote in news:f4531a1a-5c58-4235-8068-
        d11b451999fc@y5 g2000hsf.google groups.com:
        >
        >
        >>This question relates to anyone who has an come across a problem
        >>running macros on Access 2007 on Vista - particularly on the runtime!
        >>Any thoughts on this welcome indeed!
        >
        >
        How about guesses? Mine is that your install utility has erred in naming
        some directories and that security prevents running code from non-trusted
        directories and that would include directories that don't exist or are
        inaccessible. The directory system in VISTA seems markedly different from
        that of XP; if your install utility is not up-to-date then it may not take
        this into account.
        If my guess is correct, and I think it has at least one chance in a million
        of being correct, a solution might be to update your install utility and
        VISTA and XP and Office to their latest Service Packs and Updates on all
        machines involved.
        But it's just a guess.
        My other guess would be that you are doing something so incredibly bizarre
        that we can't guess what it is.
        Maybe the first guess is preferable?
        Maybe he can convert the macro to some VBA code. Then in the AutoExec
        use RunCode that calls the converted function. At least he could get
        the description of the error or step thru the code.

        If the OP's macro is calling code via RunCode...add something to the
        error routine like
        msgbox Err.Number & " " & Err.Description

        I'm surprised he gets only the error number instead of the error
        description at this time. I would think it would be the other way around.

        Awesome Aussie

        Comment

        • jackbenimble999@gmail.com

          #5
          Re: Running macros in Access 2007 Runtime on Vista

          Great news! I believe my problem is solved. It turns out the enabling
          macros to run with no restrictions was in fact the solution.

          Jack B. Nimble.

          On Feb 11, 1:21 pm, Salad <o...@vinegar.c omwrote:
          lyle fairfield wrote:
          jackbenimble... @gmail.com wrote in news:f4531a1a-5c58-4235-8068-
          d11b45199...@y5 g2000hsf.google groups.com:
          >
          >This question relates to anyone who has an come across a problem
          >running macros on Access 2007 on Vista - particularly on the runtime!
          >Any thoughts on this welcome indeed!
          >
          How about guesses? Mine is that your install utility has erred in naming
          some directories and that security prevents running code from non-trusted
          directories and that would include directories that don't exist or are
          inaccessible. The directory system in VISTA seems markedly different from
          that of XP; if your install utility is not up-to-date then it may not take
          this into account.
          If my guess is correct, and I think it has at least one chance in a million
          of being correct, a solution might be to update your install utility and
          VISTA and XP and Office to their latest Service Packs and Updates on all
          machines involved.
          But it's just a guess.
          My other guess would be that you are doing something so incredibly bizarre
          that we can't guess what it is.
          Maybe the first guess is preferable?
          >
          Maybe he can convert the macro to some VBA code. Then in the AutoExec
          use RunCode that calls the converted function. At least he could get
          the description of the error or step thru the code.
          >
          If the OP's macro is calling code via RunCode...add something to the
          error routine like
          msgbox Err.Number & " " & Err.Description
          >
          I'm surprised he gets only the error number instead of the error
          description at this time. I would think it would be the other way around.
          >
          Awesome Aussiehttp://www.youtube.com/watch?v=MvXnQ3J C-Nw

          Comment

          Working...