Re: Security/Reliability issues with Scripting Runtime

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Ken Halter (Ken_Halter_at_Use_Sparingly_Hotmail.com)
Date: 12/17/04 

Date: Fri, 17 Dec 2004 12:59:22 -0800

"Bo Gusman" <bo@bogusville.us> wrote in message
news:e3XA%23DH5EHA.3388@TK2MSFTNGP15.phx.gbl...
> The Scripting Runtime provides some very nice capabilities - the
> Dictionary, among others. One of the guys in the office told me he vaguely
> recalls an issue with his Virus scanner disabling scripting about the time
> that the I Love You virus hit. He therefore is reluctant to use the
> scripting runtime for fear that if we install it as part of our app, it
> may be disabled by a customer's AV s/w.
>
> Scripting in a browser or email client (or Word or Excel docs, for that
> matter) are trapped by most AV products these days, and it makes perfect
> sense to do so. I would be very surprised that any AV s/w will disable the
> scripting runtime DLL when it is used in a native VB6 app.
>
> He also says that there was a problem with the FileSystemObject that
> caused "Dr. Watson" crashes on an NT4 box. (I'm told that we still have
> customers running on NT4 systems, though I'm somewhat hard pressed to
> believe that.)
>
> Comments and or experiences?
>
> Bo

What is it about the Dictionary object you like? The FileSystemObject is a
pig so avoid it at all costs. VB has everything you need for file IO already
built in and fully debugged.

I don't have any personal experience but if the AV disables scripting, it
will effect your app. Thing is, once you start running script or accessing
the scripting runtime, you're passing control to that runtime.. which means,
anything that effects that runtime will effect your app. Not only that,
deployment's an issue. If you install a version that's different than the
one installed by the version of IE they're running, that could cause all
kinds of problems.... bah.... not worth it just to get a Dictionary object
imo.

fwiw, we have quite a few customers still running NT4. If you poke around
these groups deep enough, you'll find NT3.51/Win3.1 users as well. 

-- 
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

Relevant Pages

  • Re: Security/Reliability issues with Scripting Runtime
    ... >> recalls an issue with his Virus scanner disabling scripting about the time ... >> scripting runtime DLL when it is used in a native VB6 app. ...
    (microsoft.public.vb.general.discussion)
  • Re: Microsoft Scripting Runtime
    ... I don't think the scripting runtime has much do do with Access itself, ... won't be broken when my app is opened with those versions. ... Also is the Scripting Runtime included as part of the A2000 Runtime Engine ... which some of my customers use. ...
    (comp.databases.ms-access)
  • Re: Text replacement with VBA Excel in several files
    ... This would be true if the scripting runtime is not installed on your ... do you see Microsoft Scripting ... then you either have to install it or you can't use these commands. ... is it possible that this code is a VB-code and not a VBA code? ...
    (microsoft.public.excel.programming)
  • Re: InstallShield Runtime Error
    ... You may receive a "1607:Unable to install InstallShield Scripting runtime" ... error message when you try to install software in Windows XP ... MS-MVP Windows Shell/User ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Error 1607 unable to install, install shield, scripting runtime error"
    ... Install Shield is not a Microsoft product. ... install/uninstall utility created by a third-party. ... Error 1607 unable to install, install shield, scripting runtime ...
    (microsoft.public.windowsxp.security_admin)