StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17093697
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-13T17:46:04.147
FavoriteCount
0
LastActivityDate
2013-06-13T18:32:07.183
LastEditDate
2013-06-13T18:32:07.183
LastEditorUserId
603855
OwnerUserId
603855
ParentId
17093217
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
If you feed something that VBScript can use as a string to .OpenTextFile, the method will try to open a file and perhaps throw a "file not found" error. <pre><code>>> strInputPath1 = "C:\test" & "\" & "css" & "\" & "main.css" >> WScript.Echo strInputPath1 >> set f = goFS.OpenTextFile(strInputPath1,1) >> C:\test\css\main.css Error Number: 76 Error Description: Path not found </code></pre> To get an "Invalid procedure call" error, you have to pass something sinister, e.g. an Empty value: <pre><code>>> strInputPath1 = Empty >> set f = goFS.OpenTextFile(strInputPath1,1) >> Error Number: 5 Error Description: Invalid procedure call or argument </code></pre> These facts make it highly probable that you <ul> <li>either changed the content of the variable strInputPath1 between its initialization and its use in .OpenTextFile()</li> <li>or initialized a variable X and used a variable Y (Y & X may be variations of "strInputPath1")</li> <li>or initialized and used two variables of the same name in different scopes (~Functions/Subs)</li> </ul> Starting your scripts with "Option Explicit" will reduce the risk of such blunders. Added wrt "got the fso named wrong" comment: As VBScript's error messages are often hard to interpret/understand, this may be a good opportunity to reflect on "What can go wrong? What will VBScript tell me about the problem? What should I do to fix the error? How can I avoid it in the future?" Given a stringy first parameter and a typo (=> empty variable) in goFS: <pre><code>>> strInputPath1 = "C:\test" & "\" & "css" & "\" & "main.css" >> set f = goSF.OpenTextFile(strInputPath1,1) >> Error Number: 424 Error Description: Object required </code></pre> Stands to reason: Trying to call a method (. operator) without an object on the left of the dot is a no-no. Let's Set the evil goSF to an object: <pre><code>>> Set goSF = New RegExp >> set f = goSF.OpenTextFile(strInputPath1,1) >> Error Number: 438 Error Description: Object doesn't support this property or method </code></pre> Still no "invalid procedure call or argument" error. As goSF now is a RegExp, let's ignore the specific method(name) - OpenTextFile() - and see what happens if we mess up the call: <pre><code>>> WScript.Echo TypeName(goSF) >> Set ms = goSF.Execute() >> IRegExp2 Error Number: 450 Error Description: Wrong number of arguments or invalid property assignment >> Set ms = goSF.Execute(Null) >> Error Number: 13 Error Description: Type mismatch </code></pre> So my claim still stands. The error "Invalid procedure call or argument" was caused by feeding Empty to the method .OpenTextFile() called on a valid FSO.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReading file in vbscript throwing error with invalid procedure call or argument error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USEkkehard.Horner
UserOwnerUserId
1. USEkkehard.Horner
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO+1 for "Option Explicit" advice.
 singulars
 PostPostId
 PO
 UserUserId
 USseeker

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.