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???
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???
Comment