Mike,

There are several possibilities, I'll mention a couple here.

First, I'll point out the obvious -- that version control really consists of several related functions: - Restricting concurrent update access to objects (either on a file/table/dataset basis, or on a row/record/line basis). - Providing information on the most recent version of data on a system (create date, user, notes). - Providing rollback capabilities -- enabling restoration of prior states of a system or file.

Some of these capabilities are easier to implement than others. Some of the capabilities are easier to implement in some contexts (text files) than others (binary/data files).

- I've heard some mumblings about SAS coming out with some sort of version control/revision control product, possibly integrated with the workings of the SQL DICTIONARY views. The fact that some objects in the views have create times specified as dates and others as datetime makes the implementation features of this somewhat interesting.

- Depending on your platform(s) and/or access to software, you might want to incorporate a standard version control product into your solution. The more current versions of RCS (a semi-standard Unix utility, also available for Win95 and WinNT, DEC VAX/AXP) support binary files. This solution would probably involve doubling (or more) your data storage requirement (archived and 'checked out' data are accessed differently). I don't know whether or which ported versions support binary file version control. Other version control products may also be available which better suit your needs.

- SAS/SHARE, password protection, and several other features of SAS could be used to restrict access to SAS datasets (though they wouldn't provide rollback capabilities for your data).

- Buying a real database with rollback and versioning capabilities, and using SAS/ACCESS to provide access to the data. If required for processing requirements, the current view of the data could be replicated as a current SAS dataset, other versions would be supported as views or via other mechanisms.

Good luck.

>Date: Wed, 18 Dec 1996 16:35:08 GMT >From: Mike McDowell <mcdowell@MORPHEUS.COR.EPA.GOV> >Subject: Revision Control with SAS? > >Hi all, > >We want to implement a revision control system for our SAS datasets - >where we could 'check out' the latest version of a dataset, or, if >necessary, check out an old version of a dataset. Has anyone >implemented such a system (maybe using proc compare)? Any ideas >on how we might go about doing this? Most (if not all) of the >systems that I know about only do source code revision control. > >Thanks, > >Mike > >------------------------------------------------------------------------ >Mike McDowell OAO Corporation >mcdowell@mail.cor.epa.gov US EPA National Health and Environmental > Effects Research Laboratory >(541) 754-4474 Western Ecology Division >mcdowell@peak.org Corvallis, Oregon ---------------------------------------- Karsten Self / kmself@ix.netcom.com

What part of gestalt don't you understand?