Prev: How to call ORACLE function via SAS (via metadata server) not SQL pass-through
Next: PROC GLM: Contrast/Estimate
From: montura on 12 Nov 2009 13:42
Build a combobox or pmenu populated with valid ID's from a SAS
dataset.
Then you are ensured there are zero incorrect entries.

From: Nathaniel Wooding on 12 Nov 2009 13:05
Craig

Do you have SAS/AF licensed? If so, you could use it for doing error checking. It has been at least a decade since I have touched it though and I have long since forgotten what little I learned back then.

As an alternate, how much stuff are your users entering. Could you use a data step Windows statement?

Nat Wooding

-----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!
CONFIDENTIALITY NOTICE: This electronic message contains
information which may be legally confidential and or privileged and
does not in any case represent a firm ENERGY COMMODITY bid or offer
relating thereto which binds the sender without an additional
express written confirmation to that effect. The information is
intended solely for the individual or entity named above and access
by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution, or use of the
contents of this information is prohibited and may be unlawful. If
you have received this electronic transmission in error, please
reply immediately to the sender that you have received the message
in error, and delete it. Thank you.
From: "Jeff J. Voeller" on 12 Nov 2009 13:19
On Thursday, November 12, 2009 at 9:45 AM Craig Johnson wrote:

> Is there a simple way to have users enter the ID once, then force them
> enter it again for verification purposes?

It's been many years since I've done serious work with FSP, so I'm afraid
I don't have any sample code to share...but I remember FSP allowing the
creation of screen-only fields. That is, you could define a field that
was tied to the screen but was not a SAS dataset variable. This, combined
with a bit of SCL, would allow you to compare the "real" dataset variable
with the screen-only variable and raise an error if they don't match. It
will also allow you to put a normally-hidden field on the screen that can
display error or other status messages as needed.

> 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?

Yes, again using SCL...though there are probably some minor gotchas if
you're trying to query the same table you're also editing.

If memory serves, you don't need a SAS/AF license in order to write SCL
for an FSEDIT screen, but you will have to learn a small amount of SCL (a
very small amount, I think) to make this work.
From: Ya Huang on 12 Nov 2009 13:16
For your first question, how about create a second ID field, which is just
for checking.

For the second question, since I don't have FSedit licensed, I can't
test for sure. But is it possible to set the dataset option, with
id as index/unique:

data new(index=(id /unique));
input id x;
cards;
1 34
2 354
3 23
2 344
;

3 data new(index=(id /unique));
4 input id x;
5 cards;

NOTE: The data set WORK.NEW has 4 observations and 2 variables.
ERROR: Duplicate values not allowed on index id for file NEW.
ERROR: Index creation failed for one or more indexes.
NOTE: DATA statement used (Total process time):
real time 0.37 seconds
cpu time 0.00 seconds


On Thu, 12 Nov 2009 11:45:02 -0600, Craig Johnson <cjohns38(a)GMAIL.COM>
wrote:

>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: T J on 12 Nov 2009 13:54
I would recommend you take a look at this SUGi paper:

SUGI 25: Building A Better Data Entry Application Using PROC FSEDIT
File Format: PDF/Adobe Acrobat - Quick View
Derek Morgan, Washington University Medical School, St. Louis, MO ...

www2.sas.com/proceedings/sugi25/25/aa/25p010.pdf

HTH,

-TJ

On Thu, 12 Nov 2009 11:45:02 -0600, Craig Johnson <cjohns38(a)GMAIL.COM>
wrote:

>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!
 |  Next  |  Last
Pages: 1 2 3
Prev: How to call ORACLE function via SAS (via metadata server) not SQL pass-through
Next: PROC GLM: Contrast/Estimate