forum.vdsworld.com

jwfv · Posted: Mon Oct 20, 2003 12:42 pm Post subject: PIPE problems

I posted this question a couple of months ago, and have still not found a solution, so I thought I would try again:

In my apps I run several small "utility" programs that return some information from some database files. It is similar to doing a command-line SQL statement, and the output is returned via standard output or to a text file.

Currently, I am having it returned to a text file, and I then load that file to a list and manipulate the data that way. It works well, and is fast.

With VDS5, it seems I could do it much cleaner and neater using the PIPE parameter of the RUN command. However, it seems to be limited as to how much data it can return or how much @PIPE() can display. Using the Pipetest demo that comes with VDS5, you can test it by running the DIR command on a directory with lots of files - it will just return the first part of the Directory listing. (For example, I ran it on a directory with several hundred files and it only returned the files that began "A" through "D".)

I have adjusted the WAIT parameter, and have left that parameter off. Nothing seems to affect the maximum it can display.

Any ideas?

jwfv · Posted: Tue Oct 21, 2003 1:04 pm Post subject:

Anyone? Anyone? Laughing

Serge · Posted: Tue Oct 21, 2003 1:53 pm Post subject:

just to let you know that i read your post and that i can't help you...sorry Sad

serge

CodeScript · Posted: Tue Oct 21, 2003 2:40 pm Post subject:

I really doubt if PIPE thing is going to be "fixed" as it is going to be flaky anyway.
You may run the DOS window hidden/
You may look for alternatives using console API functions to get the text.
I think mindpower was doing some work on that.

vdsalchemist · Posted: Tue Oct 21, 2003 3:27 pm Post subject:

Hi All,
The work I was doing was to turn your VDS Exe into a Win32 Console application. Which it was successful Smile

The DSU I developed would actually allocate a console window for your VDS Exe and had several functions to let you manipulate that console window. I had built a simple console Compiler that would use VDS'es IDE automation to compile your source code into a Win32 console Exe. Once your VDS Exe is a Win32 console app then any other console application that you ran would run in the same console screen that your VDS Console Exe allocated. This is not the same as using Pipes. The DSU and Console compiler had no reason to use Pipes because it made your VDS Exe a Win32 console application so all output is directed to the single console window of the VDS Exe so you could scrape the console screen and use any of the text if you wanted to.

jwfv · Posted: Tue Oct 21, 2003 3:35 pm Post subject:

Thanks for the replies -

It's too bad I won't be able to use that - it would be great for running little "utility" apps that fit well for my purposes.

I run the programs hidden now and the user's experience is transparent as to the whole process. Just trying to make it even smoother ...

Thanks again.