There is value in entering a knowingly-vague bug report into the system in a case like this where a database corruption was found. Clearly the observed problem was not entirely user error and there really is a bug somewhere -- and a severe one. Even though the steps to reproduce are unknown, logging the bug can assist in finding a pattern when the same thing is reported again. The earlier database can still provide evidence in tracking down the root cause, once later bug reports come in. The number of such reports help the developers prioritize the problem against all the other issues.
Ward ----- Original Message ----- From: "Dennis M. Kowallek" <[email protected]> To: <[email protected]> Sent: Friday, January 21, 2011 2:54 PM Subject: Re: [LegacyUG] Phantom people - duplicated RINs On Fri, 21 Jan 2011 19:30:08 +0000, Ron Bernier <[email protected]> wrote: >It certainly would seem to me that it would make it much easier to fix a >problem if the user could provide repeatable steps so that the programmers >aren't chasing their tales. Sure it would. I'm just saying that if I had said that to a customer when I was a corporate developer, I would have at least been called into my boss's office (and left his office with a new "one"). As I said, apparently times have changed. *** The steps Elizabeth reported were repeatable (with her database). Would support have accepted this as a bug report? When they found the IMMEDIATE cause to be a corrupt tblNX, would they have closed the trouble report without looking into what caused the tblNX corruption? -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools http://groups.yahoo.com/group/ltools Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
