FileSystemObject

[MPM1100]

I am having to go back to an Access 97 format. In the current project we use
the FileSystemObject to reference, parse, and do other essential file
manipulations. Is there a similar method to do such things in 97?

Thanks in advance...
MPM

 

[DomThePom]

Same functionality is available by creating a reference to Microsofr
scripting runtime - go to tools references and click in the box against
Microsoft scripting runtime

 

[MPM1100]

Hello Dom...

Thanks for the info, but I'm not finding that reference in the list. Any
suggestions?

 

[Douglas J. Steele]

You can use FSO in Access 97 the same as in any other version of Access, but
what sort of file manipulations are you doing?

VBA has virtually all the same capabilities as FSO for file manipulation,
and has the advantage that you don't need to add the overhead of linking to
an external library.

 

[MPM1100]

Hi Doug,

Yes, you are correct in that VBA does offer most of the functionality of the
FSO. Just trying to save time reinventing the wheel, so to speak. Mainly
needed to parse out the file path which FSO does nicely. VBA does not offer
anything for that. It wouldn't be a big deal to write a parser, however,
other functions are already in place using that functionality and more.
Going back to 97 requires a number of code rewrites in the event FSO couldn't
be used. Regardless, I don't know what reference to use for the FSO. Would
you like to make a suggestion???

Thanks...
MPM

 

[Douglas J. Steele]

What do you mean by "parse out the file path"? You mean you have
C:\Folder1\Folder2\File.ext and you want File.ext? The Dir function does
that: Dir("C:\Folder1\Folder2\File.ext") returns File.ext.

If you're determined to use FSO, I'd strongly recommend using late binding,
so that you don't need to set a reference to it. That will make your
application a little more reliable in the case where different users have
different versions of C:\Windows\System32\scrrun.dll.