>Hi everybody.
>
>I would like to know if you use FSO.
>

Absolutely, for just about all file and file-system related functions. The primary issues are portability of code between various flavors of VB - the same code works for VB, VBA and VBScript, and the functionality is all there. And, from my POV, if added features for the file system become available, they're implemented independently of my code - late binding makes life easy; new FSO versions are external to my app, and become available as the updated FSO provider is installed on the system.

Simple examples - the Drive collection makes a great deal of information available that otherwise would require detailed API code, that may not be portable across platforms. FSO's syntax works the same cross platform.

A simple exampleis the task of testing if there's is a writable volume in a removable media drive - the IsReady method works and handles the issues of theerror handling mode of the operating system for you - API code or LLF code that works under Win9x may require a bit of juggling with the error handling mode of NT or Win2K. The current volume's File System and serial number are available directly - no half-screen of API stuff to handle the issues.

The Files and Folders collection make recursion of a tree easier and more intuitive IMO as well.

And the fact that the same (well, essentially the same) code works in other languages, too, makes it that much more attractive.