HP3000-L Archives

December 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Paul H Christidis <[log in to unmask]>
Reply To:
Paul H Christidis <[log in to unmask]>
Date:
Thu, 20 Dec 2001 11:17:02 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
I thought I had this down, but recent events make me doubt.

It was my understanding that even if one opens up a database in 'update'
mode, the 'mod' date of a dataset does NOT get changed unless a record is
added/updated (I can verify this with a plain text file and QUAD).

For the last few weeks the users of an application have been insisting that
they have NOT been making any changes to the application and I've been
insisting that someone MUST be changing something since the database was
being included in the partial backups AND since the 'mod' dates of many of
the datasets were being changed.  After some investigation, against a test
database that had not been accessed for over 2 months, I came to the
conclusion that either I've been wrong all along, or some change has
occurred in IMAGE that causes the mod dates to be updated if a dataset is
accessed and the database has been opened in 'update' mode.

Can anyone else confirm my conclusion?  Has it always been that way?

Regards
Paul Christidis

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2