Still no "invalid procedure call or argument" error. Let's Set the evil goSF to an object: > Set goSF = New RegExpĮrror Description: Object doesn't support this property or method operator) without an object on the left of the dot is a no-no. Stands to reason: Trying to call a method (. > set f = goSF.OpenTextFile(strInputPath1,1)
Given a stringy first parameter and a typo (=> empty variable) in goFS: > strInputPath1 = "C:\test" & "\" & "css" & "\" & "main.css" Starting your scripts with "Option Explicit" will reduce the risk of such blunders.Īdded wrt "got the fso named wrong" comment:Īs 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?" or initialized and used two variables of the same name in different scopes (~Functions/Subs).or initialized a variable X and used a variable Y (Y & X may be variations of "strInputPath1").either changed the content of the variable strInputPath1 between its initialization and its use in.These facts make it highly probable that you an Empty value: > strInputPath1 = EmptyĮrror Description: Invalid procedure call or argument To get an "Invalid procedure call" error, you have to pass something sinister, e.g. > set f = goFS.OpenTextFile(strInputPath1,1) OpenTextFile, the method will try to open a file and perhaps throw a "file not found" error. If you feed something that VBScript can use as a string to.
0 kommentar(er)
