>The following is my select statement.

>SELECT DATABASE.TABLE.COLUMN
>FROM DATABASE.TABLE
>WHERE DATABASE.TABLE.COLUMN = 'QT';

>When I change the where clause to be
>WHERE DATABASE.TABLE.COLUMN >= 'QT';

>Everything works fine. Unfortunately the results are not what I want.

Obviously the ">=" forces a serial read of the dataset/table which is what the
"=" SELECT should be doing if the dataitem/column is not a search item.  The
">=/<=" SELECT should work, although it's somewhat of a kludge.  Has the data
base been restructured (like removing a path from the dataset/table) and the
change not reflected in Image/SQL?  In other words, was the dataitem/column a
search item at one time, and now no longer is, but Image/SQL still thinks it is?
I haven't done a lot with Image/SQL, but I did set up a test data base for
access and I remember it was a pain to do initially, and that whenever a
structural change was made to the Image data base, the DBE had to be detached,
rebuilt, and attached all over again.

Jim Phillips
[log in to unmask]