FSO vs I/O statements

[cedx]

Greetings,

I am doing some modifications to a program that used the "write #" to generate comma delimited text files.

Currently, I am considering re-writing the codes to use the FileSystemObject object. I read somewhere on MSDN that the File I/O statements "will eventually be phased out in favor of the FSO object model". What are the pros and cons of using the FSO?

Also, since the Read method will read a specified number of characters from a TextStream file, is there another way to read comma delimited files without resorting to parsing the result of the Read method?

Thanks in advance.

[Frans C]

I wouldn't bother to alter your code. In the next version of vb (vb7 or vb.net) all file operations will be done by a new object (System.IO) so your code would need a conversion anyway.
A disadvantage of using the FSO is that any computer with this dll installed on it (scrrun.dll) is more vulnerable to virusses.

[Vlatko]

Using the FSO you will need to distribite +1 dll with your app.