Re: piping / redirecting into a vbs script ?

VanguardLH <[email protected]> wrote:
> Frank Slootweg <[email protected]> wrote:
> 
> >   FTR, AFAICT he does *not* "want files themselves to do reads and
> > writes of other files". (I think) That's your misunderstanding. The
> > 'files' are not "data objects", but a VBScript (myvbscript[.vbs]), i.e.
> > it *is* a program. That's clear by the fact that the .vbs file *is*
> > executed.

[Series of 'Duh!'s and misinterpretations deleted.]

  See my response to John. It's not about filetype association, etc.,
but about what translates <filename> to <filename>.vbs *before* filetype
association takes places, i.e. similar to (*not* 'the same as') how
<filename> gets translated to <filename>.bat.

  BTW.:

> He wants to pipe or redirect files into files, like:
> 
> textfile1 | textfile2
> textfile2 < textfile1
> 
> He discovered the solution was to specify the .vbs extension on the
> filename to get that handler to read the text file to run the script.  

  Nope, he 'discovered' no such thing. He specified the .vbs extension
*and* he added wscript.exe to interpret the .vbs file.

  One of the many problems resulting from his snipping of context.