Date:         Tue, 3 Oct 2006 17:55:04 -0700
Reply-To:     "Nordlund, Dan (DSHS)" <NordlDJ@DSHS.WA.GOV>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Nordlund, Dan (DSHS)" <NordlDJ@DSHS.WA.GOV>
Subject:      Re: Surprising retain feature
Comments: To: avi <aviben@BEZEQINT.NET.IL>
In-Reply-To:  <1159915612.212597.248910@k70g2000cwa.googlegroups.com>
Content-Type: text/plain; charset=utf-8

> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of avi
> Sent: Tuesday, October 03, 2006 3:47 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Surprising retain feature
>
> Hello,
>
> Though an quite experienced user of SAS, i was quite surprised to learn
> that in some cases, observations retain their values from one obs to
> another, without specifying the RETAIN statement
> ("When variables are read with a SET, MERGE, or UPDATE , The variables
> retain their values until new values become available").
>
> Could someone explain exactly what and why it happens and the way to
> overcome the problem thaht has caused some disturbing results in one of
> my applications?
>
>
> Thaks a lot
> Avi

Avi,

Can you give a simple example of what you are doing that has produced "disturbing results" in one of your applications and what those disturbing results are?  SAS-L may be better able to provide you with advice on how to overcome the problems you are experiencing.

Dan

Daniel J. Nordlund
Research and Data Analysis
Washington State Department of Social and Health Services
Olympia, WA  98504-5204