Mike, I have been following this thread. The way the database structure is stored in the '.RB1' file seems to preclude corruption of that file so that a TABLE becomes a view. The only way to change the sturcture of TABLES and VIEWS is via commands. I would scan all of my program code for "CREATE VIEW", "CREATE TABLE", "ALTER TABLE", "DROP TABLE", "DROP VIEW", "PROJECT" commands. Are users allowed access to the "R>" where they could issued commands to change the database structure.
Creating VIEWS within the database from a structure point of view is a complex interaction of several parts of the database. 1. An entry is created Table block of ".RB1" file. 2. Entries are created in the Column block of the ".RB1" file 3. An entry is created in the "SYS_VIEWS" datablock of the ".RB2" file along with updates to the "SYS_VIEWS" definition in the Table block of the ".RB1" file. Consequently no simple corruption of the ".RB1" file could account for what you have described. -- Jim Bentley American Celiac Society [EMAIL PROTECTED] - email (973) 325-8837 voice (973) 669-8808 Fax ---- mike <[EMAIL PROTECTED]> wrote: > Dear Bill.....I believe you are correct...it was me! I think > somebody else at that > mentioned the part about the table getting turned into a view, > but I can't remember > who. Will try ALL of the suggestions before creating the temporary > table solution. > > Mike > > Bill Downall wrote: > > > I think Mike Sinclair started the same topic in April, under > the heading > > "disappearing tables." I remembered the thread, too, and > wondered if this was > > the second person to have the problem, but it looks like it's > the same person > > reporting it for the second time. Mike, could that be what > happened? > > > > Since it appears Mike's is still the only database with this > particular problem, I > > am suspicious that it is one of three things: 1) an application > problem: drop > > table and/or create view commands hidden somewhere that Mike > has forgotten > > about and/or not found. 2) a hardware problem. I'm serious. > If, for example, > > there were a coded piece of information in the tables block > of the #1 file with a > > one bit difference between a designation of a table and a > view, then a bad pin on > > a NIC or cable could lead to information being changed in > the #1 file. (I have > > seen, for example, a table name change with a letter being > changed to another > > letter that was 2, 4, 8, 16, 32, or 64 ascii numbers lower.) > 3) Something really > > unusual about the database or application, like a reserved > word problem, that is > > resulting in this corruption. > > > > In any case, sending a copy of the before and after databases > to RBTI > > ([EMAIL PROTECTED]) is probably the best idea. > > > > Bill > > > > On Tue, 09 Jul 2002 14:15:52 -0400, mike wrote: > > > > >Dear Alastair, > > > > > >Do you recall who else had this happen? I have been searching > but I can't find > > >them! > > > > > >Mike > > > > > >Alastair Burr wrote: > > > > > >> Thankfully, I have not had this happen to me but there > have been two or > > >> three people reporting tables turning mysteriously into > views over the last > > >> few months. > > >> > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
