×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Hi John,

You use STRPCCMD to run ShellExec. (Did you see the sample code I provided??)

I doubt there's any significant difference in execution speed, between using ShellExec and using a DOS prompt (which appears to be what you were doing) but I haven't done any benchmarks, either.



John Allen wrote:
Scott,

Thanks, I will try that.
Do you know if ShellExec runs any faster or slower then STRPCCMD?

Thanks again

John

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, January 13, 2010 2:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: Using STRPCCMD with & in file name

Try invoking it via ShellExec. Something like this should work:

CHGVAR VAR(&CMD) +
VALUE('rundll32 shell32,ShellExec_RunDLL +
"\\192.168.2.60\ACCT\P&L 10-16-2009.PDF"' )
STRPCCMD PCCMD(&CMD) PAUSE(*NO)


John Allen wrote:
We have been using STRPCCMD to display PDF files in the IFS. Works great.

Just had a user create a PDF file that contained an & in the PDF file name
(P&L statement.PDF)


When using STRPCPCM to display this file we get an error. It appears the
STRPCCMD is stopping at the & character

STRPCCMD PCCMD('"\\192.168.2.60\ACCT\P&L 10-16-2009.PDF"') PAUSE(*NO)

Generates an error:

'L' is not recognized as an internal or external command


If I rename the file by changing the P&L to PNL everything works fine

I tried enclosing the & in quotes and that did not help


Any ideas?



Thanks


John






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.