LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (August 1996, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 2 Aug 1996 21:00:12 GMT
Reply-To:     "John M. Rinehart" <74134.3135@COMPUSERVE.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         "John M. Rinehart" <74134.3135@COMPUSERVE.COM>
Organization: CompuServe Incorporated
Subject:      ?? Storing FSEDIT observation values in an SCL list

Hi all,

I'm working on an FSEDIT application and want to include audit journaling, to document dataset updates (oldvalue/newvalue, etc.). I plan to store the initial and updated dataset values in SCL lists, for comparison and recording to an audit dataset. However, if possible, I would like to avoid hard-coding all the dataset variable names in assignment statements, to reduce application maintenance following changes to dataset variable names. I can of course get the get the current variable names into an SCL list, and use this to create named lists for storing the initial and updated values for each variable. But how can I actually put the dataset values into the lists, without hardcoding the window variable names in a SETNITEM_ function?

Symbolic subtitution of varible names in SCL code doesn't seem to be appropriate at runtime. Is there any way to reference the values of the current observation in an FSEDIT application other than by window variable name? An undocumented listid or something?

Any ideas would be appreciated. Thanks.

John M. Rinehart 3280 Skytop Trail, Dover, PA 17315 (717) 292-1636

74134.3135@compuserve.com


Back to: Top of message | Previous page | Main SAS-L page