I was able to resolve my issue, but have no idea why it works. It apparently has something to do
with the system path on the PC running the compiled app. I changed : ZIP cmd . exe / c MOVE & vedifile & v856file to ZIP C:\Windows\System32\cmd . exe / c MOVE & vedifile & v856file and now everything works perfectly with the compiled app on the second PC. The error variable does indeed trap if the MOVE statement was successful or not. I performed several tests and it returned a 0 or 1 depending on whether the execution was successful or failed. A very handy tool. This most likely had nothing to do with Rbase or the compiler, but something in the PC's system variables or the like. Anyway, it is working and I am on to other tasks. Thanks all. -Bob ----- Original Message ----- From: "ttc inc" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, December 7, 2010 3:31:39 PM Subject: [RBASE-L] - RE: v8 compiled app ----- Original Message ----- From: "ttc inc" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, December 7, 2010 3:31:39 PM Subject: [RBASE-L] - RE: v8 compiled app Thanks Emmitt, Yes, I have the set error var declared previously. I do need confirmation as when I wrote the code several months ago (just now moving it to another PC as compiled) I had asked the question on the list and recieved the answer that I could trap the status of the zipped command. 0=success 1= failed. I need to get confirmation if this is correct or not, as it certainly effects my code. It does seem to work as I expect at the R:>. It is after compiled that I am seeing the issue. I have not dug up the original email, but I think Bill Downal may have pointed me in the direction. (Hint.. Bill ...??) I may have misunderstood, but it did work uncompiled for some months. (I know how to dump file lists into temp tables and do a check that way, but this method is streamlined if it works) If any one can confirm the error trapping I would appreciate it. That may be why I was using ZIP instead of LAUNCH, to get the error trapping? Thanks all. -Bob ----- Original Message ----- From: "Emmitt Dove" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, December 7, 2010 1:20:05 PM Subject: [RBASE-L] - RE: v8 compiled app ----- Original Message ----- From: "Emmitt Dove" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, December 7, 2010 1:20:05 PM Subject: [RBASE-L] - RE: v8 compiled app Bob, Assuming you have: SET ERROR VAR verror … before that code, the problem is that the error variable will only tell you if the ZIP itself was successful, not the actual MOVE. You need to code a routine to copy the source file then delete the source file, testing to see if the file exists at various points. There are all sorts of ways to go about this part, many of which can be done without writing either .bat or .cmd files. If you’d like an example, contact me off-list. Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, December 07, 2010 13:18 To: RBASE-L Mailing List Subject: [RBASE-L] - v8 compiled app I have an app that runs fine from the R:>. However when I compile it, this section of code does not work the same. --copy 856 file to 856 directory ZIP cmd . exe / c MOVE & vedifile & v856file IF verror <> 0 THEN PROPERTY move856 visible 'true' ELSE PROPERTY move856 visible 'false' ENDIF vError always returns as 1 when running compiled but works as expected when running from the R>. Is the ZIP /C command not supported in the compiler? Any other thoughts? Thanks, -Bob
