Thank you for the explanation, Larry.
Mike Ramsour AK Steel Coshocton Works Quality Department Phone: 740-829-4340 Cell: 740-502-1659 From: Lawrence Lustig <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: 08/29/2012 04:28 PM Subject: [RBASE-L] - Re: INDICATOR variables Sent by: [email protected] You can use one variable name. I use vI for every one. You can even leave them out entirely (they're optional in the syntax diagram) except that you will then receive a WARNING time you have read a record that has one or more NULL values in it. Indicator variables were introduced as part of an SQL variant called Embedded SQL, intended to allow you to use SQL directly from languages such as C that cannot represent NULL values. They have no real value in a language like R:Base in which you can check the resulting variable using IS NULL directly. I only use them to avoid the needless warning message. -- Larry From: "[email protected]" <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wednesday, August 29, 2012 4:03 PM Subject: [RBASE-L] - INDICATOR variables When using a SELECT . . . INTO . . . .INDICATOR statement can just one generic INDICATOR variable be used for each value or should there be a unique INDICATOR variable for each value? For example is it OK to do this: SELECT custname,custcity,custzip INTO vname INDICATOR vind,vcity INDICATOR vind,vzip INDICATOR vind . . . . Or is this the best way: SELECT custname,custcity,custzip INTO vname INDICATOR vnameind, vcity INDICATOR vcityind,vzip INDICATOR vzipind . . . . I'm guessing unique may be better but can a generic one be used? Any and all guidance is greatly appreciated. Thanks. Mike Ramsour AK Steel Coshocton Works Quality Department Phone: 740-829-4340 Cell: 740-502-1659 Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed and may contain privileged, proprietary, or otherwise private information. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed and may contain privileged, proprietary, or otherwise private information. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.
