Re: OK. So what's wrong?

In Article <D3uIn8.8ID@cix.compulink.co.uk> Stuart Hemming writes: >I was running a program on a *new* database. I was the only informix user >on the system and I kept getting, on just the one table, > >-106 ISAM error: non-exclusive access. > >This was on an SE database version 5.01 something. > >Where *does SE record it's locks? How do I clear it? Any ideas? > It varies with the wind, or, as it were the locking method in use on the platform that you use. Check your .dbs directory and see if you have .lok files. These are getting rarer now, but if you still have them, then rename the .lok file out of the way (in case you need it) and then try your app. again (the .lok file will get created for you). If it uses the fcntl locking method (far more likely) then the only way normally is to reboot the machine. One of my old sites suffers this about once every six months. Hope it isn't a more frequent occurence with you. Regards Neil Neil S. Briscoe | The Three Stages of Life: Aldershot, Hants, England | First, you believe in Father Christmas neil@salmon.demon.co.uk | Then you don't believe in Father Christmas nbriscoe@cix.compulink.co.uk | And then, you are Father Christmas