forcing index use with OWS/NT

I am mystified. Running Online Workgroup Server on NT. D4GL front end. Have a table, POLICY, with 15 or so columns. Unique index on Polno (the policy #), duplicate index on polsetup (date) and polname (Char 35). Have a QBE screen set up. If client enters SMI* in the policy name field (polname) and queries, it does a brute force sequential search...OR uses the polno index (according to set explain). I have tried dropping the polname index and making a composite of polname/polno...and then one of polno/polname. Nada. The select statement does an ORDER BY POLNO since even though I want all the names SMI*, I want them delivered in policy order. Is this my problem? When I try this in DBACCESS with no ordering, etc, it ignores the polname index. Originally this identical query/screens/table was on old I4GL on SE and worked perfectly. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own