I have been out of the office and have not addressed the issue. Jan replied with an idea of not using a compiled app. While that might address this particular issue, I will still work on a good method for debugging compiled programs. I do not run into this often, but it does happen from time to time, i.e. works OK at the R> but not compiled. I do a lot with ODBC connections into other systems and that is were most of these issues pop up. I normally find that tweaking the syntax a little, etc. fixes the issue, but sometimes it is very hard to find and can take a lot of time, since they work OK at the R> or regular Rbase. I need to read up on the DEBUG command and consider using it.
-Bob ----- Original Message ----- From: Dan Goldberg To: RBASE-L Mailing List Sent: Friday, June 13, 2008 5:39 PM Subject: [RBASE-L] - RE: Debugging Compiled Apps I was wondering if you had come up with a solution. My e-mail was down for the last day. The reason I ask is my program is having an issue with the latest update. I am going to test the latest update vs. the previous. I have am having problems with the load command in my nightly routine. I gives a dll error and corrupts my index files. It has been the same routine for sometime but I need to test it out before reporting it to RBTI. Dan Goldberg ------------------------------------------------------------------------------ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, June 12, 2008 6:13 AM To: RBASE-L Mailing List 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 ------------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.3.0/1501 - Release Date: 6/13/2008 6:33 AM
