[WriteLog] Back-up??

[M. Edward Wilborne III]

lol... and it works for me...  I've somehow crashed WriteLog a couple of
times and was able to recover all my QSOs.

Ed
----- Original Message ----- 
From: "Mike McCarthy, W1NR" <lists at w1nr.net>
To: <writelog at contesting.com>
Sent: Wednesday, September 29, 2004 10:02 AM
Subject: RE: [WriteLog] Back-up??


> I thought that was the case.  Then why was this issue brought up in the
> first place?
>
> Mike, W1NR
>
> -----Original Message-----
> From: writelog-bounces at contesting.com
> [mailto:writelog-bounces at contesting.com]On Behalf Of A. Sewell
> Sent: Wednesday, September 29, 2004 10:00 AM
> To: writelog at contesting.com
> Subject: Re: [WriteLog] Back-up??
>
>
> Writelog DOES write a journal file.  From the Writelog help file:
>
> File Backup
> The entire QSO data base is stored in memory, but is written to disk, or
> read from disk using the File Save and File Open operations. As with
> important data on any computer, the QSO data base should be periodically
> written to magnetic storage to protect against loss of data in a power
> failure.
>
> WriteLog automatically protects newly entered, but not yet saved data. A
> separate journal file of just the QSO data is kept between Save
> operations. This journal file (with extension _jou.adi) is used in the
> case of a failure when there are QSOs that had been added to the log
> (and therefore to the journal file as well), but no Save operation had
> been used on the full data base. The recovery is automatic: just do a
> File Open of the WriteLog file you last saved and WriteLog will offer to
> recover the QSOs in the journal file.
>
> Whether you chose to recover the journal or not, WriteLog renames the
> journal to <filename>_bck.adi (where <filename> is the name you have
> chosen for the file.)
>
> WriteLog deletes the journal file at the end of a successful Save
> operation, so the journal file contains only those QSOs that do not
> appear in the newest WriteLog file.
>
>
> 73,
>
> Alan  N5NA
>
>
> Mike McCarthy, W1NR wrote:
>
> > The best way to handle this is to have a "journal" file which stores
> all
> > QSO's from the last save.  If there is a crash, when WriteLog starts,
> it
> > restores the QSO's from the journal after reading the main database
> > file.  This is basically what word processing and spreadsheet programs
> > do between saves.  This would require some internal programming.
> >
> > Mike, W1NR
> >
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>