Subject: | |
From: | |
Reply To: | |
Date: | Sun, 8 Aug 1999 02:03:22 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Stan Sieler <[log in to unmask]> wrote:
>Stephen writes:
>> Someone correct me if I am wrong, but if you do an unload /reload would not
>> the chain still be intact?? I am under the impression that the
>
>Not necessarily ... DBUNLOAD will optionally unload in SERIAL manner ...
>which will not preserve the chronology of the entries in chains.
Correct.
>A chained (non-SERIAL) DBUNLOAD followed by a DBLOAD would preserve
>chronology of the chains (although individual entries in different
>chains may not be in the same order, relative to each other afterwards).
Correct, but incomplete. A chained DBUNLOAD followed by a DBLOAD
would preserve chronology of the *primary* chain; all bets are off
for any additional chains defined within the detail set.
>But...I'm not sure because of one word: ADAGER. I haven't used DBLOAD/DBUNLOAD
>for a longggg time.
My company uses DBChange, but the same principle applies. And for those
"Oh, forget it, I'll unload/load the database anyway" moments, I usually
use the old-reliable-standby Dictionary utilities DICTDBU and DICTDBL with
their ability to use a disc-based unload file (as opposed to DBUNLOAD
and DBLOAD insisting on a tape).
--
Mike Reaser, Atlanta, GA, USA B2f+tw+dcvg+kvs++l+
ICQ 36141307 If it's there, remove the YOUKNOW to, well, you know
"Ignorance" is as much a method of computer security as "Hope" is a
method of birth control -- K. Ward/L. Joynes
|
|
|