No triggers, thanks. But you may have hit on something. What if someone disabled the index, then a program opened the file, the index was enabled, but the program still has that file open and thinks the index is still disabled? That might explain a great deal.
I have removed the index and rebuilt it - several times. I've deleted the X item from AIX and started the whole deal all over. No change. Today, the DISABLE.INDEX command is temporarily MIA. This is to rule out someone manually entering this command. And now we watch. Thanks for the ideas. I appreciate the feedback. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 25, 2005 6:59 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] DISABLE.INDEX from BASIC What does the L_filename look like? It stores all of the records written to the file while the index was disabled. Perhaps a permission issue on it? Is the file in use while you are doing this? The disable.index won't come into effect on a file until it is closed in basic - perhaps that's also true of enable.index. Perhaps a trigger on the file is keeping it "open." The basic command INDICES() may also provide some more info/clues. At this stage you may have to remove the index and rebuild it. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
