> I'm getting an "invalid procedure call or argument" every time I try
> to take control of a collection of files that I've grabbed. With this
[quoted text clipped - 28 lines]
>
> Thanks for the help.
Hello bgetson,
I assume you have set a reference in your VBA project to the Windows
Script Host Object module, since you are using early binding. Instead
of dimensioning objFiles As Files, change it to a generic object: Dim
objFiles As Object. The Workbook.Open requires the file name string to
be fully qualified if it is in a different directory than the current
one. Use the Path property for this.
Dim wkbk1 As Workbook, wkbk2 As Workbook
Dim objFSO As FileSystemObject
Dim objFiles As Object
Set objFSO = New FileSystemObject
Set objFiles = objFSO.GetFolder(strFolder).Files 'strFolder is some
path
Set wkbk1 = Workbooks.Open(objFiles(1).Path)
Set wkbk2 = Workbooks.Open(objFiles(2).Path)
Sincerely,
Leith Ross
bgetson - 29 May 2008 08:41 GMT
Leith, thank you for your suggestion, but that still hasn't seemed to
solve my problem. You're right, I added the reference to "Microsoft
Scripting Runtime." However, in my process, the invalid call/procedure
is being tagged on objFiles(1). It would give me the same error if I
called: Set f = objFiles(1) or Set f = objFiles.Item(1). Dimensioning
objFiles as a generic Object didn't seem to solve this issue.
Any other ideas?
Leith Ross - 29 May 2008 08:46 GMT
> Leith, thank you for your suggestion, but that still hasn't seemed to
> solve my problem. You're right, I added the reference to "Microsoft
[quoted text clipped - 4 lines]
>
> Any other ideas?
Hello bgetson,
I missed an important argument assigment when looking at the Item
property, It takes a KEY value or in this case the Name of the File to
work. Bit different from a regular Item property for a collection. The
only way to access unknown files in the collection is to use For
Each...Next.
For Each f In MyFiles
Workbook.Open f.Path
Next f
Sincerely,
Leith Ross