Is using Windows scripting, especially for FileSystemObject, a good idea?

Question

I was recently asked to do some maintenance on the VB6 app. This is due to some I / O files. I find the I / O operations offered by the link to the Windows host script and using FileSystemObject is much friendlier than the I / O operations that come with VB6.

But will this cause problems due to security issues or because the host script will be disabled on some users computers?

Update (August 20, 2012): Asking this question, we encountered the problem of non-functional scrrun.dll three times among 3000 clients. We had to fix them manually using remote support. It seems that sometimes the vivazhchik is to blame.

Answer 1

As Robert Harvey noted in his comment, in practice this is usually not a problem. It is possible that it scrrun.dllmay not be installed or registered correctly on this machine. We encountered both scenarios when installing our own VB6 application on client machines.

, , ( Microsoft InfoPath) , InfoPath ( -) VB6 DLL, WSH FileSystemObject, , -, script, VB6. , WSH , , .

Windows Scipt - WSH, FileSystemObject, VB6.

Answer 2

IO VB "" - Q/BASIC, , / ( //). , FSO, , , .

, -, , FSO .

Answer 3

, FileSystemObject , -, - -, -. FileSystemObject, .

FileSystemObject VB6 API Windows API. , Karl E Peterson - VB6 , VB6.

• Read .
• , .
• , .
• , .
• .
• /