Prev: How to call ORACLE function via SAS (via metadata server) not SQL pass-through
Next: PROC GLM: Contrast/Estimate
From: Derek Morgan on 13 Nov 2009 10:03
On Nov 12, 4:16 pm, cjohn...(a)GMAIL.COM (Craig Johnson) wrote:
> I'm digging through the various responses.
>
> Nathaniel Wooding
>
> Do you have SAS/AF licensed? =96 Thanks to working at a University yes I do
> but right now I have 26 different FSEdit screens. =85half of which are
> modified for second entry that compares it against the first.  I=92m trying=
>  to
> avoid having to create anything else new.
>
> Could you use a data step Windows statement? =96 If I was sure what that wa=
> s
> maybe!
>
> Ya Huang and Michael Raithel
>
> I=92m familiar with database construction so I=92m giddy at the idea of lin=
> king
> datasets together.  I=92ll definitely have to do some reading up on this.  =
> A
> couple of questions:
>
> 1)      You can define FK/PK=92s etc after the data set has been created,
> correct?
>
> 2)      If entry error occurs it will show up in the log but what about
> during the data entry on FSEdit? Does an error flash or beep or something? =
>  I
> need to let my data entry people know that there is an error.
>
> Jeff J. Voeller
>
> I was seriously pondering doing using a created field before I posted.  I
> was just trying to avoid it if there was a slicker way to do it.
>
> Montura
>
> Seriously considering using a combo box or pmenu with valid ID=92s,  I just
> have to figure out how make them.  I have the SAS Screen Control Language
> version 6 book but it doesn=92t have much in there.  Looking at the net I
> haven=92t found a simple enough example I can work with understand and port
> over to the actual apps.
>
> TJ
>
> I actually had the paper open. J I=92ve referenced it several times.  The
> issue is that when you are just starting out (say you=92ve been using SAS
> since April) you tend to have issues stripping out code manipulating it and
> then getting it work.  I=92m a pup at this stuff but I=92m getting better.
>
> Which brings me to=85..
>
> Derek Morgan
>
Sorry, my fault. I'm changing jobs so some stuff is still where it
used to be and some isn't. I'll try to put it somewhere you can find
it tonight.

From: Derek Morgan on 13 Nov 2009 10:46
On Nov 13, 9:03 am, Derek Morgan <derek.wustl....(a)gmail.com> wrote:
> On Nov 12, 4:16 pm, cjohn...(a)GMAIL.COM (Craig Johnson) wrote:
>
>
>
> > I'm digging through the various responses.
>
> > Nathaniel Wooding
>
> > Do you have SAS/AF licensed? =96 Thanks to working at a University yes I do
> > but right now I have 26 different FSEdit screens. =85half of which are
> > modified for second entry that compares it against the first.  I=92m trying=
> >  to
> > avoid having to create anything else new.
>
> > Could you use a data step Windows statement? =96 If I was sure what that wa=
> > s
> > maybe!
>
> > Ya Huang and Michael Raithel
>
> > I=92m familiar with database construction so I=92m giddy at the idea of lin=
> > king
> > datasets together.  I=92ll definitely have to do some reading up on this.  =
> > A
> > couple of questions:
>
> > 1)      You can define FK/PK=92s etc after the data set has been created,
> > correct?
>
> > 2)      If entry error occurs it will show up in the log but what about
> > during the data entry on FSEdit? Does an error flash or beep or something? =
> >  I
> > need to let my data entry people know that there is an error.
>
> > Jeff J. Voeller
>
> > I was seriously pondering doing using a created field before I posted.  I
> > was just trying to avoid it if there was a slicker way to do it.
>
> > Montura
>
> > Seriously considering using a combo box or pmenu with valid ID=92s,  I just
> > have to figure out how make them.  I have the SAS Screen Control Language
> > version 6 book but it doesn=92t have much in there.  Looking at the net I
> > haven=92t found a simple enough example I can work with understand and port
> > over to the actual apps.
>
> > TJ
>
> > I actually had the paper open. J I=92ve referenced it several times.  The
> > issue is that when you are just starting out (say you=92ve been using SAS
> > since April) you tend to have issues stripping out code manipulating it and
> > then getting it work.  I=92m a pup at this stuff but I=92m getting better.
>
> > Which brings me to=85..
>
> > Derek Morgan
>
> Sorry, my fault. I'm changing jobs so some stuff is still where it
> used to be and some isn't. I'll try to put it somewhere you can find
> it tonight.- Hide quoted text -
>

Oh, I also have some ID selection code and a forms menu code that you
can use. What version of SAS do you have?

From: Randy Herbison on 13 Nov 2009 11:42
Craig,

Can you avoid ID errors, during data entry, by preloading them?

If not, here's one way to get a selection list from which users can choose an ID. allIDs is an ID master file, completedIDs is the table edited interactively (row-level edit) via FSEDIT.

Sorry, my SAS/FSP is rusty. I haven't created a SAS/FSP application since the early 90s.

-Randy

length cmd $ 12;

fseinit:
control allcmds;
return;

init:
return;

main:
cmd=upcase(lastcmd());
if cmd='IDMENU' then do;
submit sql continue;
create table toDo as
select ID
from allIDs
where ID not in(select ID from completedIDs);
endsubmit;
dsid=open('toDo');
id=datalistn(dsid,'ID','Please select one');
dsid=close(dsid);
end;
return;

term:
return;

fseterm:
return;

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of Craig Johnson
Sent: Thursday, November 12, 2009 12:45 PM
To: SAS-L(a)LISTSERV.UGA.EDU
Subject: FSEdit Question

I created some code that allows us to use double data entry. After running
through our first batch of forms I've found two common entry errors.
First, I found users are entering the wrong ID #. That then trickles down
to the verification process and causes problems when we then can't match on
ID #. Although I've created code to check for ID's that don't match, I'd
rather institute some code that minimizes the problem. Is there a simple
way to have users enter the ID once, then force them enter it again for
verification purposes? Links to examples would be helpful if it is possible
as I'm new to the whole FSEdit front.



Second, is there a simple way to query the ID against the SAS data file to
check to make sure it hasn't been entered? I'm finding a chunk of duplicate
entries I shouldn't have either. Again, links to examples or sample code
would be helpful.



Thanks!
From: Craig Johnson on 16 Nov 2009 09:32
I was out of the office last Friday but plan on spending today working on
the issues.

Below are my preliminary plans.....

1) IC on the files (remove possibility of duplicate errors)
2) Drop down menu of ID's in SAS/FSP
3) Updated paper copy log sheets they use to enter data prepopulated with
info needed so all they need to do use check boxes

Answers to other questions..........

1) Derek I'm using SAS 9.2 and I have the most updated version of all the
stuff that goes with it. I just don't have physical books for all of it.
First  |  Prev  | 
Pages: 1 2 3
Prev: How to call ORACLE function via SAS (via metadata server) not SQL pass-through
Next: PROC GLM: Contrast/Estimate