IT sounds like it is time to do a 'DELETE.INDEX', 'CREATE.INDEX', 'BUILD.INDEX'. There must be something out of sync and you may never figure out the why. We have had indexes that produced different results when using 'REQUIRE.INDEX' and 'NO.INDEX'. The only way to go forward was to rebuild. We now have a database of our Unidata indexes and a program to do this rebuild if the need arises. - Rod
-----Original Message----- From: Kevin King [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 11:12 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] DISABLE.INDEX from BASIC Okay, it's definitely NOT DISABLE.INDEX. The problem has occurred again, but with a slightly different manifestation. LIST.INDEX shows the indexes are enabled, built, and no updates pending. However, when I select the file using that indexed field, I get nothing. If I disable the index and execute the exact same select statement, I get 28 records. Here's the selection statement, and yes, it's Prelude: SELECT BIN.QUEUE WITH BTREE_DEFAULT = "001!002!O]" Again, this is UD 5.2 on AIX, and DISABLE.INDEX isn't even around as a verb from TCL. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
