I use IF-THEN-ELSE when I have a comparison with one of two outcomes; it is simple and easy to understand/follow. For situations where there are lots of choices the SWITCH works better than having multiple IF-THEN-ELSE commands (nested or not). For the simple comparison where either would work, I am not sure there is a performance advantage using one over the other, but I would be inclined to use the IF-THEN-ELSE construct.
Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. Chitiea Sent: Saturday, January 31, 2015 12:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Performance: IF/ELSE/ENDIF v SWITCH/ENDSW Listers: I've successfully coded the same critical piece of a tiny, single user development database both ways. In your experience, are there any performance advantages for one over the other, were this a live, monster, multi-user database? As ever, much appreciated. Bruce Chitiea SafeSectors, Inc. eCondoMetrics eWaterMetrics 909.238.9012 cell --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
