Date:         Mon, 18 Feb 2002 07:07:12 -0500
Reply-To:     Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Subject:      Re: Data Entry in SAS - best way to enter concurrently??

On Mon, 18 Feb 2002 09:14:10 -0000, Philip Mason
<philipmason@WOODSTREET.ORG.UK> wrote:

>I am updating an FSEDIT application which allows for clinical data entry
>within SAS. It is quite a good application which includes the ability to
>generate SCL code for validation at point of entry from metadata (and
>much more). It is currently implemented on Windows in SAS 6.12 - though
>moving to v8 soon.
>
>What is the best way to enable this for concurrent data entry? The
>options that come to mind are:
>
>1 - Purchase SAS/Share and use that.
>2 - Implement my own file/record locking system in SAS code (Base and/or
>SCL)
>3 - Buy SAS/Access to *something* and move the database into Oracle or
>SQL Server (or one of many others). Providing the chosen database allows
>concurrent multi-user update and it can be used via the access engine
>then that should work.
>
>Considerations are (as always): cost of software, cost of
>implementation, cost of maintenance.
>
>Are there other options? I wonder what those who have examined this
>issue would recommend.
>
>Thanks
>
>Phil Mason


My question is: do you really need concurrent update for that? Concurrent
access in my opinion you need, where time critical needs are given. E.g. a
reservation system for something, where it is necessary for all accessors
to get the actual situation reflected in realtime.
If some persons are entering clinical data - is that really time critical
or isn't it possible to enter the data individually and combine the parts
afterwords?