If I select more than 64K documents for processing, the client crashes - this never used to happen. Is there any way around this - I am working with very large databases - around 2 million documents.Thanks - Tim
Subject: Had no problem selecting over 500,000 documents
So presumably the problem is not the selection, but what you’re doing with them after you select them. To suggest a workaround, it would be helpful to know what you’re doing and at what point the process fails.
Also, please report all crashes to Lotus Support so we can look into them.
Subject: Crash after selecting 64k documents
Thanks. The system crashes in the course of selecting - once I have selected 64,000 documents using the tick selection column and continue selecting, with or without a break, the system just crashes without any warning. Glad to hear that it is not a design feature!
Subject: I don’t suppose you have a view Onselect event…
I’m going to give you the same advice I give everyone who runs across a crash – contact Lotus Support, give them your NSD, explain to them how to reproduce the problem. I don’t like crashes, and they’re given high priority for fixing, especially when they affect end users, as in this case (developers, not quite so much).
Subject: No - this is a completely standard view
HiMy apologies for the delay in responding - I have not been doing large selections for a while. Just did a selection and as soon as it went over 64,000 Notes died. I am not doing anything other than selecting and the view itself, and the database, use the design of the Personal Address book as a starting point, so perhaps there is something in there in the indexing perhaps? Notes dies everytime as it reaches the 64.000th document.