Ray and Mike,
I may be missing the point regarding the signifigance of the date,
but the work around I've tested here, and which we will use is as follows:
* Set the clock back to Jan 1970 (or '80, one or two decades retrospectively
to the curent date)
* Use our current filename system which comprises a 3 letter day/date code
(e.g. jan 1st 1997 is 7aa, Feb 23 1998 is 8bw (27 to 31 of month uses
numerals 1-5)). This can expanded if it is important to access files for
more than a decade
As each file has the filename written in the $FIL field, you can always
check when a file was created and ignore the date. e.g.
FCS1.0 256 1319 1536 61535 0 0
$TOT: 15000
$BTIM: 16:15:58
$ETIM: 16:17:45
$FIL: 7KZSH015
$DATE: 11/26/97 **** Any "accepted" date here who cares ??****
$DATATYPE: I
$MODE: L
$NEXTDATA: 0
$BYTEORD: 4,3,2,1
$SYS: BD - LYSYS II Version 1.0 11/90 - HP Pascal 3.22
So essentially my point is this, provided you can track when the file was
actually made, be it by a filename system, or a filename and retrospective
date combination, then what's the problem?
Geoff
======================================================================
Geoffrey Osborne | ____ __ o Ahh!
Flow Cytometry (FACS LAB) | __ `\ <,_
John Curtin School of Medical Research, | __ (*)/ (*)
Australian National University, | ==============|
CANBERRA, AUSTRALIA. | |--|
Email: Geoff.Osborne@anu.edu.au | |--|...
Phone: 61 2 6249 3694 |
FAX: 61 2 6249 2595 |
-----Surfing the Web?: Try http://jcsmr.anu.edu.au/facshome.html------
======================================================================
This archive was generated by hypermail 2b29 : Wed Apr 03 2002 - 11:50:23 EST