OK, now this is interesting ... Ken McGinniss asked me for a small example database where I have seen this happen.
I went back to the database it was happening with, to the same general group of people in fact. I couldn't make it mess up this time (tried about 5 times). Now, I have to admit that the problem before occurred after I had been running Legacy for a couple of hours or more. So my working hypothesis is that this is one of those "tired program" problems, as I call them, that only manifest when the program has run long enough to cause a serious memory or other resource leak, or to corrupt itself or one if its components (.dll, .ocx files, etc.). Possibly even the database engine itself. I've seen that happen enough times, with bewildering and bizarre results (and I am not just talking about Legacy here, Netscape does it too, for example) that I should not be surprised. Next time something weird like this comes up, I will exit the program and restart it before I call out a bug! (Well, it is a bug, but probably not in the program itself at all!) To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
