My concern with omitting the "IND" is that, based on previous history,
at some in the future R:Base might tighten up the syntax and require the
IND. Then you've got to crawl through and update all your code. Also,
including the IND will make your code a touch more readable for the next
hapless soul who looks at it.
Doug
On 5/16/2012 10:52 AM, Albert Berry wrote:
Karen, I don't even bother with the IND and just use the i1 for the
variable. I should probably just put an i there, but it's hard to notice.
SELECT Col1, Col2 into vAVariable i1, vAntother i1
Albert
On 16/05/2012 9:13 AM, [email protected] wrote:
Albert: I hear ya! I'm probably a bit OCD on wanting to see the
least amount of code necessary to do the task. And when I see
someone's code like this:
select column1, column2, column3 into
vColumnVar1 INDICATOR vColumnVar1Indicator,
vColumnVar2 INDICATOR vColumnVar2Indicator ....
and then they never use the indicators for anything, it drives me crazy!
What's wrong with
select column1, column2, column3 into
vColumnVar1 IND iv1, vColumnVar2 IND iv1
Karen
In a message dated 5/16/2012 9:39:18 AM Central Daylight Time,
[email protected] writes:
I simply create a variable i1 and use that on every variable in a
select
into. The same null indicator on every variable works for me, and takes
up very little room in RBEdit.
Albert
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2012.0.2176 / Virus Database: 2425/5001 - Release Date:
05/15/12
