Solved(?) Weird ISQL Problem

Hi again; I don't know if you all remember, but a few days ago I posted a query for info about the UPDATE statement in ISQL causing a database to self-corrupt. I received no responses, except from Walt, who pointed out a number of interesting things to me. Thanks, Walt!!! Anyway. I re-ran the ISQL in question on a slightly earlier version of ISQL (4.00.UD2) on an SS1 (running SunOS 4.1.1), and guess what? It worked fine. I have since heard rumors about a 4.0 bug under SunOS 4.1, requiring the use of ISQL 4.1; unfortunately, the Informix support folks have not yet come through with my contracts, so I can't comment if this is the problem. So, the moral of the story; use the CHECK TABLE command regularly, and use it religiously if you're in the SPARCStation ELC SunOS4.1.1 ISQL 4.0 camp. Chris Hermansen Timberline Forest Inventory Consultants Voice: 1 604 733 0731 302 - 958 West 8th Avenue FAX: 1 604 733 0634 Vancouver B.C. CANADA clh@tfic.bc.ca V5Z 1E5 C'est ma facon de parler.