Dave, This is a bit of a wild guess, but F3, LIST, and Object Manager probably all build their lists from the internal system view that looks like a system table, SYS_TABLES. There is probably only one table, but an illegal extra row in some interal system table is making it look like their are two.
Try OUTPUT mytable.STR UNL STR FOR tablename OUTPUT SCREEN and see what you get. Also, look for too many of some kind of constraint or index: LIST CONSTRAINTS FOR tablename See if the NOCHECK option helps you dropp the table: DROP TABLE tablename NOCHECK Bill On Fri, 26 Oct 2001 17:30:32 -0400 (Eastern Daylight Time), David Ebert wrote: >I've discovered that I have two tables by the same name in one database (via >LIST, Object Manager, and F3). > >How can this happen? It won't let me drop the table (resource unavailable), >but I assume I could reload the database and have the duplicate not picked >up. > >My primary concern is prevention. > >tia > >Dave >
