🚀 go-pugleaf

In article <4936@tellab5.tellabs.com> wiseman@tellabs.com (Jeff Wiseman) writes:
> [Stuff about D&S Archives deleted...]

>For safe D&S'ing always remember:
>
>1) Never, never, never disperse twice into the same account (or you'll get the
>drity database problem)
>
>2) Frequently run the save-as and in the subsequent session, use a duplicated
>copy of the save-as file. This keeps the database "neat" and seems to reduce
>the number of problems that occures (as well as forces you to do backups :-).
>
>3) Even though it is possible, avoid editing from non asset or non liability
>accounts.
>
>4) Beware of accidently using a descriptor in an account that it was not set up
>for (can cause DB screwups)
>

This is pretty scary stuff. This set of "work-arounds" seems to be rather
extensive. Do the databases really get trashed so easily? Frankly, number 2
seems to imply that D&S will trash its database at the least possible excuse
and also seems to be a real pain in the rear to do.

I was considering buying D&S, but after hearing this, I am thinking again.
Does anyone else have similar experience that backs up what Jeff says? Is
there a later version of D&S that fixes the problems that these workarounds
are designed to avoid? How about it Monogram? Did you guys really release
a program that eats its databases as often as the above workarounds imply?


Matt Hardin
matth@locus.com

-------------------------------------------------------------------
I speak for myself only. My employer neither knows nor cares.
-------------------------------------------------------------------