Jan you have a point and I would like to add a question/comment/thought here. Thank you.
Let's say you have a .rff and it is on the server, running in compiled mode. It is in the Windows startup and it looks for updates and etc.. gives you status and not real memory hungry here, in fact the user could even kill the process and/or have a timer. Then it is possible to distribute your updates every time somebody logs on to the server. They see a new version and you have a command that checks the versions they have! You could also include your stats that you collect with 'cval' and note any problems. (I have a little ugly process that grabs about 10 'cval's now program version, map, memory, ip address, nic etc..) I really have to think about this in the background, but if anybody has done such a thing! Please let me know. It would have to be rff and form timer preferred application. If nobody has I think in a week or so I will and if anybody would like a copy just email me. Sincerely, Paul Dewey p.s. Perhaps it is also late at night and I am very tired! And I will read this tomarrow and say "What was I thinking" p.s.s. "A computer lets you make more mistakes faster than any invention in human history--with the possible exceptions of handguns and tequila." - unknown New Horizon Interlock Inc. New Horizon Safety Diagnostics Inc. www.interlockinfo.com Saving Lives - One Breath at A Time T This e-mail message is intended only for the named recipient(s) above and is covered by the Electronic Communications Privacy Act 18 U.S.C. Section 2510-2521. This e-mail is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you have received this message in error please immediately notify the sender by return e-mail and delete this e-mail message from your computer. From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Johansen Sent: Thursday, June 12, 2008 7:15 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Debugging Compiled Apps Bob, I have taken a different approach to this. I don't use a compiled application for automated tasks. I have a full version of R:Base installed on the server. I create an RMD file in the RBase directory. I create a bat file in the root directory which calls the RMD. I create a scheduled task to call the the bat file and make sure that the appropriate permissions are assigned to the task. Now if problems occur (the usual one is forgetting to SET ERROR MESSAGE 2059 OFF when no rows are found) I just pull up a simple text editor and make the changes needed and we are back in business. Hope it helps. Jan ----- Original Message ----- From: [EMAIL PROTECTED] To: RBASE-L Mailing List <mailto:[email protected]> Sent: Thursday, June 12, 2008 6:12 AM Subject: [RBASE-L] - Debugging Compiled Apps On occasion, I have an app that when I run the .cmd file at the R> all works perfectly, then I compile the very same .cmd with no changes and it does not work. Normally these apps run via the scheduler and do not have any screen input or display, i.e. data compiling routines such as with EDI transactions. I run the cmd through trace and all shows OK, but then again it runs OK at the R>. I am looking for suggestions on methods others use to debug the program after it is compiled into an exe. Remember, there are no user inputs or screen displays on this particular app, which is normal for my scheduled programs running data routines. Thanks, -Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441
