The only way that I know that this can happen is if the server crashes or is re-booted, without flushing memory to disk. In other words, the user makes the changes, which are stored in memory. Everything looks good. The server is re-booted or crashes, without writing the memory to disk. When the server comes back up, the old version, which is still on disk, is now the current version.
Pretty rare, to say the least, but it has happened. -------------------------------------------------- Charlie Rubeor Senior Database Administrator Wiremold/Legrand 60 Woodlawn Street West Hartford, CT 06110 Tel: 860-233-6251 x3498 Fax: 860-523-3690 Email: [EMAIL PROTECTED] -------------------------------------------------- Pamela J Robbins <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/21/2007 12:44 PM Please respond to u2-users@listserver.u2ug.org To u2-users@listserver.u2ug.org cc Subject [U2] WRITE issues?? Has anyone seen a problem like this? The user claims they changed a record, then checked to make sure it actually changed. They find everything updated, but on checking days later, finds the data back in it's original state. We've had several claims like this over the past week and a half and it's with different sets of programs. Could it be a hardware failure? TIA, Pam -- Pamela J Robbins New Bolton Center Senior Programmer Analyst School of Veterinary Medicine [EMAIL PROTECTED] University of Pennsylvania 610-925-6438 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
