SE 7.12 CREATE TABLE leaves orphaned constraints on error

If a CREATE TABLE statement running under SE 7.12 attempts to create constraints with names that already exist, it aborts the CREATE TABLE and leaves the constraints in table sysconstraints. These are difficult to delete as there is no entry in systables to get at them through an ALTER TABLE or DROP TABLE statement. Is this an inevitable side-effect of not being able to rollback SE DML statements or is there a way of avoiding the problem? I have already thought of checking all the new constraint names against sysconstraints.constrname (a nuisance), manually altering the sys tables (NOT a preferred option) and reloading the database (tedious). I know I could move to OnLine but it seems like a sledgehammer to crack a nut. Any helpful suggestions gratefully received. -- Peter Lancashire Information Systems Specialist, Bayer plc Eastern Way, Bury St Edmunds, Suffolk, IP32 7AH, UK Tel: +44-1635-562258, Fax: +44-1635-562281 Mail: Peter.Lancashire.PL1@bayer.co.uk --- My Internet plumbing does not allow me to mail and post news together. Sorry. All opinions are my own and not those of Bayer plc. --- Join Infuse, the UK Informix User Group at http://www.infuse.co.uk/