<br><br><div class="gmail_quote">On Mon, Jan 14, 2013 at 12:43 PM, Kenneth Brody <span dir="ltr"><<a href="mailto:kenbrody@spamcop.net" target="_blank">kenbrody@spamcop.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 1/13/2013 6:12 PM, Dan McCabe wrote:<br>
[...]<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I change ">/dev/null" in my menu script or my processing to >nul or<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
\device\null, I get a filePro error telling me I have a bad command on the<br>
</blockquote>
command line. The error always points to the ">"<br>
</blockquote></div>
[...]<br>
<br>
That makes no sense, since I have never seen Windows ever give an indicator as to where it thinks the error is.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But, since you are saying that it's a filePro error, I am going to go out on a limb and ass/u/me that this is a SYSTEM command within processing, and not a menu command line, and that filePro is complaining about a syntax error in your processing, totally unrelated to the command you're trying to execute.<br>
</blockquote><div><br></div><div>Ken, your assumption is correct. I knew what I meant, but didn't articulate it properly. The filePro error is the result of a system command. The menu script doesn't produce a filePro error.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If my assumption is correct, please show us the actual prc line you're using.<br>
<br></blockquote><div> ::show popup ("5","-1") "TEMPORARY FILE COMPLETED, PROCESSING REPORT":</div><div> :ry eq "P":ha = cd <"Rtime -m rpt -v paysel -f pay -y payauto -r \"reg\" -rw \""{we{"\" -a -u" <hz:</div>
<div> :ry eq "D":ha = cd <"Rtime -m rpt -v paysel -f pay -y payauto -r \"reg\" -rw \""{we{"\" -a -u -pv" <hz:</div><div> :ry eq "P":system ha < "> nul":</div>
<div> :ry eq "D":system ha </div><div> ::gosub cleanup: </div><div><br></div><div>RY is a user input field; cd is the path to run rreport. WE is the week ending date the user selected.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
However, the point is moot, as redirecting stdout on Windows won't cause filePro's output to disappear. (The Windows console API won't allow redirection to a file. Nor will it work with redirecting stdin from a file.) </blockquote>
<div><br></div><div>I did not know that. That explains why it isn't working.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Have you considered using "start /min" to run the command in a minimized window?</blockquote>
<div><br></div><div>I haven't because I have never heard of that, this is my first foray into any programming on Windows, I've been using filePro on UNIX for 25 years. Is that possible from within processing? </div>
<div><br></div><div>Dan</div></div><br>