Not necessarily.
Many years ago we were getting periodic corruption of table and column names at one location. After much examination over a period of months I finally figured out that characters were always being changed by the same hex value. For instance, an 'a' would become a space or some other character. But the difference between them in the ASCII chart was always the same. I finally traced it to one PC that had the non-maskable interrupt turned off. The NMI's function was to detect memory corruption on the motherboard. Well, we had flaky RAM in one spot. Since this was DOS, and since things always loaded in the same sequence, the particular area of memory was always holding the copy of file 1 in that region of memory. When the PC went to update file 1 and the memory was in the wrong state, bad data was written to file 1, either in SYS_TABLES or SYS_COLUMNS. Replaced the memory and all was well. Point it, it can absolutely be traced to something hardware or network related. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, August 19, 2010 14:17 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Corrupt DB Is the corruption always happening in the same table? If it is, then it is hard to make a case that it's something hardware or network related... Karen
