Nikos, I found that on major search operations (doing a search on vast volumes of folders/files) often results in the resulting scrap pane just suddenly vanishing from your screen.
Haven't been able to pinpoint what exactly is going on. You'll find last piece of DBMON output when this happens below, but it doesn't seem to show anomalies
Maybe it has to do with the very long folder names it tries to search??
I have also seen this a couple of times, but in my case x2 also closes. Absolutely no system-error messages, though; nor a messgae that x2 has generated error, and Dr. whatshisname would close the application.
there's a stack overflow error lurking somewhere when searches get really deep. I'll have to do something about it. I don't think it is related with the debug build either
I didn't check how far that search had progressed, or even whether it had collected any results at all. Logically, it should have collected a lot of results, because it ran for quite a while before crashing..
I was working on something else, when the error window popped up.
On NT4, x2 can pass through deep directories in my C:\ drive (FAT32) without crashing: (I could count 14 layers of folders). In C drive, I can search repeatedly with different parameters without any problem whatsoever.
(But in the same PC, it crashed when searching in NN.)
BTW I was wrong about the depth in NN PCs: Some of the NN PCs have really deep directories (>10 levels).
How are the PCs taken up for scanning? Alphabetically? Then the very first PC has a very deep structure, which x2 could have crossed without crashing (because, as I said earlier, it crashed after a very long time).
So what is critical here?
>> Depth?
>> Number of folders searched?
>> Number of files searched?
>> Filesystem (FAT32 vs NTFS)?
>> Local vs NN?
Not my fault, really: after we started getting virus via shared folders, we trimmed sharing to bare minimum (if at all). But now our admin has merged some sub-networks in the organization; and the other guys haven't followed the same precautions.
I was simply not aware of this.
But if you are willing to flog my Network Admin instead, you will make a lot of people happy!
*****
Rather than leave us guessing, why don't you give us a special debug version?
In large searches, the DBMon log becomes monstrous. Can you modify it to catch/retain only the last few lines? This is an old technique, used in diagnosing problems in electronic circuits.
)
