Hi Jessica,

sorry for answering only now: but I just found you message only today.

To answer your questions:

1. Using Scripting.FileSystemObject is definitely good practive, if you are working for MS Windows based systems. With it you can do everything you usually do manually with the Windows Explorer like create / delete files and folders, read files or write to them etc. Also you can have collections like all files in folder etc.
There are lots of examples how to use the FileSystemObject in a help file called VBSCRIP5.CHM or VBSCRIP6.CHM depending which version of VB you are using. Also it can be instantiated in a straight forward fashion of MS automation methology (all examples take from the mentioned help-files, which also contain a tutorial): With (all examples taken from these help files)

  Set oFSO = New Scripting.FileSystemObject

you can create a FileSystemObject with quite a few properties and methods. With

  Set oRoot = fso.GetFolder("C:\")
  Set oFolders = oRoot.SubFolders

you can create a FoldersObject, which is a collection of all folders in the root. With

  For each oFolder in oFolders

you can manipulate each folder. With

  Set oFolder = oFSO.GetFolder(cFullyPathedFolderName)

you can create a FolderObject for a specific folder. With

  Set oFiles = oFolder.Files

you can create a collection of all of the files contained in a folder, so that with

  For Each oFile In oFiles

you can manipulate each of them. And so on ...

2. You should include scrrun.dll in the installtion package, which goes into

  %SystemRoot%\SYSTEM32

and has to be registered (install shield does this for you)

That should do it.

Hans

>Dear All,
>
>We are using the File Scription object in our software. I would like to know whether using the scription object is a good practice or should it be avoided. Secondly, when building a setup in install shield what are the support libraries that need to be included for the scripting object.
>
>Thanks in advance.
>
>JD.