Albert, I agree with you and Karen. Part of the problem is that R:Base has been very forgiving in the past and programmers have become complacent. Properly programmed code will, in all likelihood, do fine when versions change. On the other hand, sloppy code is a ticking time bomb waiting to bite the program in the rear end.
Q&D (quick and dirty) code and non-standardized code have uses during development but should not be included in production applications. I keep a set of files, x1.rmd, x2.rmd and so on, where I place snippets of code I need to quickly test, but once the code has been debugged and tested, I make sure that it meets standards and is properly commented before being transferred to the application. I have almost completely converted code all my old code when I moved to 7.5, and it has worked well for me; upgrading to Extreme 9.0 should be fairly straight forward. When in doubt, I always follow the "P" rule: Proper Prior Planning Prevents Poor Performance. Javier, Best regards, Javier Valencia, PE Principal Valencia Technology Group, LLC 14315 S. Twilight Ln. Suite #14 Olathe, Kansas 66062-4571 913-829-0888 Office 913-915-3137 Cell 913-649-2904 Fax [email protected] Confidentiality Notice This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately at 913-829-0888 or by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Albert Berry Sent: Friday, May 14, 2010 10:01 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Scratch Karen nailed it, I think. As she does, I only use SQLCODE to check for end of data. All other places I use the error variable and capture variable. Albert [email protected] wrote: > Aha! I could be wrong, but "edit using" is not a sql command, > therefore it > does not evaluate properly using "sqlcode". As Bill stated in an earlier > email, trapping for sqlcode should only work for an actual sql command > (such as > select, insert, update). "edit using" is an RBase command to bring up > a form... > > Karen > > >> Forgot to say there are no triggers, just a simple Edit using form, >> if sqlcode <>0 then, Enter using form. >> Tom Hart >> >> >> >> >
