Ben: As a matter of my own personal practice, I do all the de-bugging, scrubbing and tracing on the ASCII files; Only after the code has been thoroughly tested, I CODELOCK it. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS 66062-4571 (913)829-0888 (913)649-2904 FAX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Petersen Sent: Friday, February 21, 2003 11:48 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Trace/Crashing - Razzak's Reply > One thing I would suggest is to do a global replacement with RBEDIT > and change .APX to .APP and the run the trace for the plain ASCII > (.APP) file. As Dennis pointed out, it is possible that CODELOCK did > not compile the file correctly, running it uncompiled would certainly > eliminate that possibility. Shoot! (read ...) You mean you can run command blocks in the APP file? All these years I thought it had to be codelocked! Ben Petersen On 21 Feb 2003, at 11:03, Javier Valencia wrote: > Dennis, Dan: > I concur that switching to the standard single quote is an excellent idea as it > prevents future (and present) compatibility issues. I would also suggest > switching to the standard _ and % instead of ? and * for single and > multiple replacements. However, since most of the command file seems to run > correctly, I suspect that this is not affecting Codelock; although a small part > of the code could be affected/corrupted. > > >From TRACE help: > ------------------------------- > The TRACE command starts the R:BASE interactive debugger. It allows you to > go through the command file line-by-line to facilitate debugging the code. > The TRACE command must be on a line by itself and not combined with other > commands. For TRACE to work correctly with a file encoded by CodeLock, the > ASCII file must be present in the current drive and directory, and have the file > extension of .APP. If TRACE cannot find the ASCII file, it does not go through > the procedure file line-by-line when it runs. ------------------------------- > > One thing I would suggest is to do a global replacement with RBEDIT and > change .APX to .APP and the run the trace for the plain ASCII (.APP) file. > As Dennis pointed out, it is possible that CODELOCK did not compile the file > correctly, running it uncompiled would certainly eliminate that possibility. > Grasping at straws...but who knows... Javier, > > Javier Valencia, PE > President > Valencia Technology Group, L.L.C. > 14315 S. Twilight Ln., Suite #14 > Olathe, KS 66062-4571 > (913)829-0888 > (913)649-2904 FAX > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dennis > McGrath > Sent: Friday, February 21, 2003 10:30 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Trace/Crashing - Razzak's Reply > > Dan, > > > $COMMAND > > inform2 > > SET ERROR MESSAGES OFF > > CLEAR V i* > > SET V imessage = + > > "You may search based on any known information. Just click + > > on the field you do have information about and fill it in. Then hit > > enter. + > > You only need to fill in one field" > > You are using non-standard quotes. Codelock assumes the single quote. > > You have two options: > > 1. Put SET QUOTES="""" at the top of the first command block of every > command file: > > $COMMAND > inform2 > SET QUOTES="""" > SET ERROR MESSAGES OFF > > 2. Go throught the work to convert to single quotes. It is worth the > trip, but time consuming. > > Dennis McGrath >
