Runtime error has occurred

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Joseph Macari

    #1

    Runtime error has occurred

    Using Acess2003; when writing code, etc. and when attempting to use the help
    files while in visual basic window, I recently started to get this message-
    "A runtime error has occurred. Do you wish to debug? Line 114 Error:
    Operation is not allowed when the object is closed." So if I hit the Yes
    button a "Just-In-Time debugging window" comes up with the following choice-
    Possible Debuggers-New Instance of Microsoft Script Writer"...when I hit the
    yes button, a Microsoft Script Editor window appears (in design mode).,,etc.
    , mentioning a few passages about ADODB and code that I'm not familiar with,
    and the name at the top of the debugging window is
    "mk:@MSITStor.. ..ks/ofvbanli.js"... hmmm...
    I started to think is this some kind of virus?? anyways, if I just say no,
    I don't want to debug, and close the original dialog box, everything returns
    to normal....the help files work ,etc..It just is a hassle that this thing
    just pops up when searching in help files. This does not happen with help
    files in the normal help window (database window)....
    I did a repair on Office; I haven't tried other mdb's until I can verify
    whats happening here...Has anybody had similar situations when using the
    visual basic window help files???


  • Wayne Morgan

    #2
    Re: Runtime error has occurred

    The help files are HTML format help files. Go to your Internet Properties
    (with IE open, go to Tools|Internet Options...). On the Advanced tab, check
    to see that Disable Script Debugging.... (there may be more than one) is/are
    checked. Also, uncheck "Display a notification about every script error".
    Click Ok and see if the problem still occurs. These boxes will get changed
    if you install FrontPage so that you can debug code you write for web pages
    in FrontPage.

    If that doesn't fix it, then I suspect that there is something wrong with
    the help files and an uninstall/reinstall is probably in order.

    --
    Wayne Morgan
    MS Access MVP


    "Joseph Macari" <jmacari1@cox.n et> wrote in message
    news:m82tf.2311 12$0l5.80668@du keread06...[color=blue]
    > Using Acess2003; when writing code, etc. and when attempting to use the
    > help files while in visual basic window, I recently started to get this
    > message- "A runtime error has occurred. Do you wish to debug? Line 114
    > Error: Operation is not allowed when the object is closed." So if I hit
    > the Yes button a "Just-In-Time debugging window" comes up with the
    > following choice- Possible Debuggers-New Instance of Microsoft Script
    > Writer"...when I hit the yes button, a Microsoft Script Editor window
    > appears (in design mode).,,etc. , mentioning a few passages about ADODB
    > and code that I'm not familiar with, and the name at the top of the
    > debugging window is "mk:@MSITStor.. ..ks/ofvbanli.js"... hmmm...
    > I started to think is this some kind of virus?? anyways, if I just say
    > no, I don't want to debug, and close the original dialog box, everything
    > returns to normal....the help files work ,etc..It just is a hassle that
    > this thing just pops up when searching in help files. This does not
    > happen with help files in the normal help window (database window)....
    > I did a repair on Office; I haven't tried other mdb's until I can verify
    > whats happening here...Has anybody had similar situations when using the
    > visual basic window help files???
    >[/color]


    Comment

    • Joseph Macari

      #3
      Re: Runtime error has occurred

      I did what you suggested; the problem still exists...though a a different
      dialog box comes up.."Internet Explorer script error"......I also went into
      Front Page app and made some changes in the macro menu, but that did not
      help. I really don't feel like reinstalling Office so I may just live with
      the problem......Th anks for your help.

      -Joe


      "Wayne Morgan" <comprev_gothro ughthenewsgroup @hotmail.com> wrote in message
      news:Bc3tf.3595 $UF3.1046@newss vr25.news.prodi gy.net...[color=blue]
      > The help files are HTML format help files. Go to your Internet Properties
      > (with IE open, go to Tools|Internet Options...). On the Advanced tab,
      > check to see that Disable Script Debugging.... (there may be more than
      > one) is/are checked. Also, uncheck "Display a notification about every
      > script error". Click Ok and see if the problem still occurs. These boxes
      > will get changed if you install FrontPage so that you can debug code you
      > write for web pages in FrontPage.
      >
      > If that doesn't fix it, then I suspect that there is something wrong with
      > the help files and an uninstall/reinstall is probably in order.
      >
      > --
      > Wayne Morgan
      > MS Access MVP
      >
      >
      > "Joseph Macari" <jmacari1@cox.n et> wrote in message
      > news:m82tf.2311 12$0l5.80668@du keread06...[color=green]
      >> Using Acess2003; when writing code, etc. and when attempting to use the
      >> help files while in visual basic window, I recently started to get this
      >> message- "A runtime error has occurred. Do you wish to debug? Line 114
      >> Error: Operation is not allowed when the object is closed." So if I hit
      >> the Yes button a "Just-In-Time debugging window" comes up with the
      >> following choice- Possible Debuggers-New Instance of Microsoft Script
      >> Writer"...when I hit the yes button, a Microsoft Script Editor window
      >> appears (in design mode).,,etc. , mentioning a few passages about ADODB
      >> and code that I'm not familiar with, and the name at the top of the
      >> debugging window is "mk:@MSITStor.. ..ks/ofvbanli.js"... hmmm...
      >> I started to think is this some kind of virus?? anyways, if I just say
      >> no, I don't want to debug, and close the original dialog box, everything
      >> returns to normal....the help files work ,etc..It just is a hassle that
      >> this thing just pops up when searching in help files. This does not
      >> happen with help files in the normal help window (database window)....
      >> I did a repair on Office; I haven't tried other mdb's until I can verify
      >> whats happening here...Has anybody had similar situations when using the
      >> visual basic window help files???
      >>[/color]
      >
      >[/color]


      Comment

      Working...