Thanks for the idea, but when you run a batch file, you by default cause a 
DOS/Command window 

to open up, even when done via Launch.  By running the EXE directly, you can 
avoid having the 

DOS window pop up altogether.  (At least that is what I am seeing in my other 
apps calling exe's 

via launch... no pop up windows) 



Thanks again, 

-Bob 





----- Original Message ----- 
From: "Buddy Walker" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Wednesday, April 13, 2011 6:04:19 PM 
Subject: [RBASE-L] - Re: Launch Question 







----- Original Message ----- 
From: "Buddy Walker" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Wednesday, April 13, 2011 6:04:19 PM 
Subject: [RBASE-L] - Re: Launch Question 




Tom 

  Try creating the bat file on the fly. 



  Create all of your variables and then 



set var vParameters = (.vquote + ‘-0’ + .vdoublequote + ‘Test.dat’ + 
.vdoublequote  +   etc ) 



  DEL myBatFile.BAT 

  OUT myBatFile.BAT 

   WRITE somefile.exe .vParameters 

  OUT TERMINAL 



  LAUNCH myBatFile.BAT 



Buddy 









From: [email protected] [mailto:[email protected]] On Behalf Of 
[email protected] 
Sent: Wednesday, April 13, 2011 6:33 PM 
To: RBASE-L Mailing List 
Subject: [RBASE-L] - Re: Launch Question 




Good idea, but alas, no change.  The double quotes still get misplaced. 



The parameter has to have the double quotes in the line as they are part of the 
parameter itself.  So setting my Rbase quote setting is not the issue.  (Thanks 
for the idea though Steve V.) 



It is definitely the double quotes.  Using the batch test suggestion below, I 
can pass  xxx*  fine, but 

not a xxx "test".  When doing the second example, the last double quote gets 
pushed to the front of the 

parameter line.  I.E.   "xxx "test 



I will keep experimenting.  



-Bob 






----- Original Message ----- 
From: "Mark Lindner" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Wednesday, April 13, 2011 5:08:04 PM 
Subject: [RBASE-L] - Re: Launch Question 

Try building the string using all variables for the quotes that are embedded. 



Set var vdoublequote = (char(34)) 

Set var vquote = (Char(44)) 



set var vParameters = (.vquote + ‘-0’ + .vdoublequote + ‘Test.dat’ + 
.vdoublequote  +   etc ) 

That way the quotes and doubles wont confuse it. 




Mark Lindner 
Lindner & Associates PC 
400 Hunnewell St, Needham MA  02494 
PO Box 920435 
Needham MA  02492 0005 
781 247 1100  
Fax 781 247 1143 
EFAX 857 366 9691 
Toll Free   888 658 4269 
Direct 781 247 1160 

THIS IS A COMMUNICATION FROM A DEBT COLLECTOR 

-----Original Message----- 
From: [email protected] [mailto:[email protected]] On Behalf Of 
[email protected] 
Sent: Wednesday, April 13, 2011 6:03 PM 
To: RBASE-L Mailing List 
Subject: [RBASE-L] - Re: Launch Question 




Excellent suggestion on the batch test!   

I did this and see that all the parameters are being passed, but not quite 
correctly. 



The parameters are sent as this: 



-0 "Test.dat" -r -S "*SRA" 192.168.0.83:1000 



but the batch file displays that the double quotes got misplaced.  It reads: 



"-o "Test.dat" -r -S "*SRA 192.168.0.83:1000 



For some reason the last double quote located after SRA is being pushed to the 
front of 

the parameter string.  Or at least that is the way the batch file is reporting 
it as such. 



Thanks again.  It is pointing me to the issue anyway. 



-Bob 





----- Original Message ----- 
From: "Dave McCann" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Wednesday, April 13, 2011 4:54:44 PM 
Subject: [RBASE-L] - Re: Launch Question 

Bob: You CAN use launch to run EXE files and parameters, I do it with a text 
editing program and pass the filename for it to open as a parameter.   You 
didn't say what exactly happens so I assume you just see nothing going on? 

One simple thing to check is the path of your EXE, is it in the directory where 
your database resides?  Perhaps there is trouble finding the EXE file.   If you 
launch without parameters what happens?  Does the EXE run? 

Another thing you might do is setup a simple batch file such as: 
rem TEST.BAT with parameters 
@echo off 
echo beginning of test 
echo %1 
echo %2 
echo %3 
echo %4 
echo %5 
echo end of test 
pause 

Use the batch file name in place of the EXE in your launch and it will display 
what parameters are getting passed to the batch file which might help you find 
out if one of the parameters is not getting passed as you expect (like the 
quotes). 


On 4/13/2011 1:36 PM, [email protected] wrote: 




My day to ask questions!   I need to launch an external program with 
parameters.  Here is my code: 



set var vLaunch = 'HTTPGET.exe' 
set var vParameters = '-0 "Test.dat" -r -S "*SRA" 192.168.0.83:1000' 
set var vLaunch = (.vLaunch  & '|' & .vParameters & '|W') 



Launch .vLaunch 





It does not work.  Are the double quotes allowed in the parameters? 



Any other thoughts? 



Thanks again, 



-Bob 



Reply via email to