And on the subject of tight coding, how particular are the "masters" about using IDQUOTES? I was wondering how much difference they can make in the grand scheme of things?
Thoughts, comments or suggestions? Mike Ramsour AK Steel Coshocton Works Quality Department Phone: 740-829-4340 Cell: 740-502-1659 From: [email protected] To: [email protected] (RBASE-L Mailing List) Date: 08/29/2012 04:08 PM Subject: [RBASE-L] - Re: INDICATOR variables Sent by: [email protected] I always use the same name for every indicator variable. The datatype is always integer so no conflict there. Unless you plan on checking the indicator variable by name, I know of no reason why the names should be unique. Karen In a message dated 8/29/2012 3:04:02 PM Central Daylight Time, [email protected] writes: 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. 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.
