See my idea on IdeaJam http://ideajam.net/IdeaJam/P/ij.nsf/0/BB7503B0846D659C8625758A001FFA49
Sorry, wanted to post a response to http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/c68f2515dcc4e4a8852574b200725e9c?OpenDocument&Highlight=0,daos instead of creating a new topic.
Subject: Interesting idea
Your suggestion is greatly appreciated, but unfortunately, it’s not possible with the current arrangement. DAOS captures the number of references to a given NLO, but not what NSF the individual references are from. As a result, a full recount is necessary when a discrepancy is detected.
Assume there is a single NLO with references from two NSF files. Say a.nsf holds 2 references, and b.nsf holds 3…all we record in daoscat.nsf is that “ABCD1234.NLO has 5 references” If a discrepancy is detected with b.nsf…and you rescan it and find 1 reference…what do you do to the count?
The worst thing that DAOS can do is to delete an NLO before all references to it are really gone. As a result, we have to be very conservative about the accounting in order to avoid that.
Don’t lose hope though, there are some ideas we’re working on that could greatly reduce the impact of these discrepancies and the necessity for a full resync.
Subject: Thanks for explaining <>