Prev: corrupted file? Help. A clue?
Next: SoldX ?
From: John Pollard on 6 Dec 2009 12:53
Andrew wrote:
> One thing that I do wish Q had (maybe there is such information that
> is being maintained for internal debugging purposes?) is a audit
> trail of changes being made to the database. I realize that Q is
> relatively simplistic in the database functions...but more
> sophisticated dbs maintain a log so that one can rollback (or
> forward) a series of changes from a particular point. That sort of
> information in some human-readable form (even if not able to be
> programmatically applied to an old copy of the qdf) would have helped
> me on occasions in the past.

That sounds like the "audit trail" I mentioned in my previous post.

> Have you ever entered a transaction, heard the kaching sound, then
> realized what you just did is not what you think you modified, but
> not you have no way of knowing what you just changed??

I would be happy to make use of such a "log" if it were present.

But I keep backups of my last 7 uses of Quicken plus at least a month's
worth of Quicken's "weekly" automatic backups. If I really need to know
what a transaction looked like before I changed it, or deleted it, or what
my account looked like sometime in the past; I can usually restore a
backup to a temporary folder and lookup the transaction there.

A "log" would make it somewhat easier to answer questions and repair data,
but probably not be a panacea. I think it would likely also introduce
problems of its own. [I don't know of any such log currently being
created.]


--

John Pollard


First  |  Prev  | 
Pages: 1 2
Prev: corrupted file? Help. A clue?
Next: SoldX ?