No problems. What about putting a "wrapper" around the disable.index command to log how it's being run?
What about ODBC access to the account? I'm not sure what it can do to the index but.... Colin Alfke Calgary, AB >-----Original Message----- >From: Kevin King > >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 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
