Karen: I have an application that runs every nigh from the Windows Scheduler. The code for the executable is:
-- Code for Load_Fuel.dat CONN PMSDB EDIT USING fuel_auto_load DISC EXIT RETURN -- End of Code All the code is contained in the After Start EEP. There are lots of PAUSE 4 commands that update the status meter for each iteration. The last few lines of this code are: PAUSE FOR 1 USING 'UPDATING SCREEN' + CAPTION 'PROCESS PROGRESS...' icon attention LABEL done CLOSEWINDOW RETURN Which closes the Form and then the database is disconnected and exits the application. It used to run as: C:\RBTI\RBG75\RBG75.EXE -r Load_Fuel.dat And now it runs as a compiled application. No noticeable difference in time of execution between the batch file and running the application from the R> prompt. Of course, there is the time up front to start R:Base from the batch file or the compiled application, but once it is up, it runs very fast. Javier, Javier Valencia 913-915-3137 ________________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 04, 2008 4:10 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Running 7.6 code from a batch? Larry: Runs in a window. There's probably 10 pause messages, nothing more... Oddest thing. 1 minute within RBase, 10 to 12 minutes if from a batch file that calls the same program.... Karen << Bob: We actually haven't even put it in the scheduler yet! We are planning on it, but running the code from the batch file from the OS command prompt runs about 10 to 20 times slower than running the code natively from within RBase. >> Is there a lot of screen output during the processing? Are you running in a Window, or DOS full screen mode? If there's a lot of screen output, the virtualization of the screen while windowed could possibly be affecting the performance. -- Larry
