FileSystemObject object

[Mudface]

I tend to use this quite a bit as it exposes a lot of useful properties and methods, however Mr Monkey in the thread below couldn't set a reference to the Scripting runtime library (Scrrun.dll) required to use it. I've used it extensively (always with early binding for convenience) with no problem on pc's with different OS's ('98, NT and 2000), and have always assumed the dll was part of the Windows system files. Can this not be taken for granted?

http://www.mrexcel.com/board/viewtopic.php?topic=21362&forum=2&8
This message was edited by Mudface on 2002-09-06 09:51

 

[XL-Dennis]

This message was edited by XL-Dennis on 2002-11-15 20:09

 

[Tommy Bak]

Hi
Since it's very easy to write a virus that can make use of Windows Script Host, a lot of people choose not to install it or deinstalls it, so as Dennis say's You cannot be sure that it's installed.
Dennis's check is nessecary.
regards Tommy

 

[Mudface]

Thanks, guys that's very useful info. I guess I've been lucky insofar that all my site's pc's are 'standard' so if it runs on mine, it'll run site-wide, but I'll bear in mind what you've said for future replies to questions on here.

I was toying with the idea of consolidating all the routines I have into a general-purpose, stand alone VB app. I take it the package and deployment wizard would incorporate the necessary file, negating the possibility that a user wouldn't have it installed?

 

[XL-Dennis]

Mudface,

I was toying with the idea of consolidating all the routines I have into a general-purpose, stand alone VB app. I take it the package and deployment wizard would incorporate the necessary file, negating the possibility that a user wouldn't have it installed?

Well, it´s may be a workable way however there might be some "watch-out" aspects with it:

- If You only need to add the SCRRUN.DLL or the whole package of WSH?

- If WSH is already installed and You install a different version of the DLL-file then already exist?

- You need to registrate the Active-X (dll-file)

I don´t know for the first two issues perhaps someone else can give the answers.

Kind regards,
Dennis

 

[Ivan F Moala]

Hi Mudface

Just to add to the above.
VB does most of the commands that the FSO
does so use VB Native commands 1st. If you
must use a method of the FSO that you can't
get from VB (?? there is usually always a method) then as above just check 1st by setting a reference and checking the error
eg (One of many ways!)

<pre/>
On Error Resume Next
Set ID = ThisWorkbook.VBProject.References
ID.AddFromGuid "{420B2830-E718-11CF-893D-00A0C9054228}", 1, 0

If Err.Number <> 32813 And Err.Number <> 0 Then
MsgBox "Error Number:= " & Err.Number & vbCr _
& "Error Discrp:= " & Err.Description & vbCr & vbCr, _
vbMsgBoxHelpButton + vbSystemModal, _
"Reference Error", Err.HelpFile, Err.HelpContext
End If
Set ID = Nothing
</pre>

 

[Mudface]

God, it's a minefield :wink: ).