OPTIONS CASE INSENSITIVE

>Mike Teachworth writes: >Unfortunately, there is no OPTIONS CASE INSENSITIVE for the CONSTRUCT >statement, >so the only way to solve the problem is to upshift those char fields in >the .pers. That way >INPUT char data is upshifted, and the CONSTRUCT where string is upshifted >too. >The only thing is that imported data must be upshifted before insertion >into the table. I believe you can give up hope on the "OPTIONS CASE INSENSITIVE" stuff. Your problem would be a sequential scan; you can't index case insensitive. If you want to preserve the form of user input (ie smith/Smith/SMItH) you could create another indexed column (called cap_name) that is all CAPS. All queries would be upshifted and looked up based on cap_name. Your imported data would either need a preprocessor that creates cap_name or you would need to run an update statement (ie update cust set cap_name = UPSHIFT(last_name)). My two cents. || ======= **** **T* ======= ||John Regep || **** **** ||Store Systems Developement || **** *R** ||Kmart Corporation || =========== ********* =========== ||3100 West Big Beaver || ***A* **** ||Troy, MI 48084 || **** **** ||(810) 643-5078 ||=============== *M** **** ===============||uunet!kmart!jregep