Date: Wed, 15 May 1996 19:28:23 GMT
Reply-To: Clark Roberts <us026486@INTERRAMP.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Clark Roberts <us026486@INTERRAMP.COM>
Organization: PSI Public Usenet Link
Subject: Re: Data Entry Screens
Dr D Chalmers <dc31666@GGR.CO.UK> wrote:
>Calling all FSEDIT Gurus:
>Does anyone know if it is possible to build FSEDIT screens, incorporating
>field attributes (capitalisation, range-checks, required etc.), by using
>statements from open code instead of using the interactive screen
>I am currently in the middle of writing a data-entry application which will
>look at the database and create its own screens.
>I've looked in 'SAS/FSP Software Usage and Reference' but unfortunately it
>doesn't seem possible to do this type of non-interactive screen creation. I
>wondered if there's any un(der)-documented features, something along the
> (in my dreams...!!!)
> > proc fsedit data=derek.test screen=derek.test label;
> > attrib weight min=50 max=100;
> > run;
>Thanks for any help.
Although I haven't actually tried this, it would be the way I would
approach the problem.
1. Create a permanent default FSEDIT screen.
2. Use PROC CPORT on the catalog entry where the FSEDIT screen is
stored to create an ASCII representation of the FSEDIT screen.
3. Determine where the fields you want to control are located in
ASCII CPORT file (this is the hard part, since documentation
for the layout of these files is not
available - outside of SI)
4. Write a datastep to manipulate the desired fields.
5. Then use PROC CIMPORT to recreate the FSEDIT screen catalog
Decision Analytics, A SAS Quality Partner
e-Mail firstname.lastname@example.org or email@example.com
Voice/FAX/Message: (619) 565-9998
Pager: (619) 975-0758