Vista - runtime error: "Object required"

Please help me. I am getting the following error on the 4th line of
the code: 'Object required: 'oFSO"
I have tried different things and it does not work.

Thanks,
SA


Sample code
-------------------
dim folderP, oFile, oFSO, fab
folderP=Application.PrimaryDirectory 'gives path of the project folder
C:\temp\Projects\21038Ax1aDx"
set oFile = oFSO.GetFile(folderP)
fab = mid(oFile.Name, 2, 4)

<karsagarwal@xxxxxx> wrote in message
news:a8b6d3d7-655d-4c5c-860b-75beba14d7c7@xxxxxxYou forgot to create the oFSO object:
Set oFSO = CreateObject("Scripting.FileSystemObject")
You will also need to create an Application object.

Hi,i am missing something like...

Set oFSO = CreateObject("Scripting.FileSystemObject")

Dirk

On Feb 16, 3:47*pm, "karsagar...@xxxxxx" <karsagar...@xxxxxx>
wrote:You need to instantiate an object before it is used (except for those
known to be provided by the host application). That is, in a
standalone WSH script you need a line like ...

set oFSO = CreateObject("Scripting.FileSystemObject")

In some other application, like Word or Excel as implied by your use
of Application - which is really VBA, not VBSscript), it can be done
in the same way, or by referencing the correct library and then using
early binding in the Dim statement, but that is out of scope here, I
think.

Of course, after you solve that problem, you're going to face others,
since I see at least two other syntax problems in the code snippet you
posted:

1. The line that reads [C:\temp\Projects\21038Ax1aDx"] is not valid
code, and

2. set oFile = oFSO.GetFile(folderP) will throw a run time error,
since the GetFile function expects the path to a FILE, not a folder.

You'll have to sort those out as well.

Good luck,

Tom Lavedas

On Feb 16, 1:12*pm, "Dirk Stegemann" <dsgra...@xxxxxx> wrote:Well, when I add the line as shown above it gives me a new error on

line 2: set oFile = oFSO.GetFile(folderP).

Error msg is " File not found". I don't understand what is missing
here but would like to add that folderP is just a variable that holds
the directory path and I need the 4 chars stating in position 2 from
the directory name. So I am thinking that I infact do not even need to
create a FileSystemObject or use the GetFile here.

For example if folderC is "C:\temp\Projects\21038Ax1aDx" I need to
extract 1038 from folderC.



Thanks,
SA.

<karsagarwal@xxxxxx> wrote in message
news:734ad3be-71a4-441d-bca2-7f53616c277d@xxxxxx
On Feb 16, 1:12 pm, "Dirk Stegemann" <dsgra...@xxxxxx> wrote:Well, when I add the line as shown above it gives me a new error on

line 2: set oFile = oFSO.GetFile(folderP).

===> since that looks more like line three, I'd suggest you reply with an
EXACT copy of the script as it now exists.

Error msg is " File not found". I don't understand what is missing
here but would like to add that folderP is just a variable that holds
the directory path...

===> that may be what you intended it to contain. But perhaps you should
display the value of the variable to make sure that the "Application" object
is returning what you think it should in its ".PrimaryDirectory" property.

and I need the 4 chars stating in position 2 from
the directory name. So I am thinking that I infact do not even need to
create a FileSystemObject or use the GetFile here.

For example if folderC is "C:\temp\Projects\21038Ax1aDx" I need to
extract 1038 from folderC.


===> FSO may indeed not be required, however, it does include various
methods for unambiguously extracting components of a path, like the base
file name. If you want to parse the full path name on your own go ahead.

/Al


Thanks,
SA.

Hi,

--
For example if folderC is "C:\temp\Projects\21038Ax1aDx" I need to
extract 1038 from folderC.
--

First of all i think it would be a good idea to read Tom's and Pegasus's replys carefuly.

I had to read about application.primaryFolder...
I think somthing similar to this would be app.path in vb or GetFolder(".")
This is the folder where the script resides.

here is a little sample....

Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oFolder = oFSO.GetFolder(".")
MsgBox mid(oFolder.Name,2 ,4) ' Shows mid(2,4) of the actual folder
For Each sFolder In oFolder.Subfolders 'Walks the subfolders..
If MsgBox("mid (Foldername, 2,4) is """ & mid(sFolder.Name,2 ,4) & """" _
, 1, "OK") <> 1 _
Then WScript.Quit
Next

HTH

Dirk

"Dirk Stegemann" <dsgrafik@xxxxxx> wrote in message
news:OAQ9vVIkJHA.5124@xxxxxxHi, Dirk
There are many ways to start a vbscript. For some of these ways,
oFSO.GetFolder(".") sometimes can return the folder object that contains the
script's source file. Of course, if the script has set up a WScript.Shell
object, it could change its CurrentDirectory property so that it no longer
matches the folder that contains the script. Or if the script is started by
dragging a file to the icon for the .vbs file, the current directory will
almost never be the folder that contains the script.

To get around these problems, I use code like this to set the current
directory to be the folder containing the script (after having created the
shell and fso objects):
objShell.CurrentDirectory = _
objFSO.GetParentFolderName(WScript.ScriptFullName)