Change of Logging Status: Implications?

Dear Informix Experts, I just discovered that a large and complex application is running against a database with no logging. Needless to say, the whole application is written without transactions, which has been causing numerous consistency problems in the database. The developer has been catching most of these problems by giving support to the users over the phone and manually cleaning up after crashes, but this is now getting out of hand. I had to convince her that using transactions is mandatory, but I'm worried about the implications of changing over the database to logging mode. It is a large application with thousands of lines of code and using lots of cursors. I know that there are several things you can only do inside a transaction when the database is defined with logging, but I'm not sure I know all of them. So I need info about the implications of changing a database to logging mode. What problems are to be expected in what parts of a program? I'll have to assist the developer throughout the migration process, without knowing too much about the program itself and the database involved. If I did know, I'd probably quit my job as DBA... These problems have grown historically without me having had much influence, so please refrain from comments like "you should have known better". I just have to save as much as possible. Database Engine is ONLINE 5.03, the application is written using ESQL/C 5.01 and 4GL 4.10. All of this is running in client/server mode with both client and server running on SNI RM400 machines under SINIX 5.42B. Answers like "RTFM" are welcome as long as the tell me which FM to R. Regards, Richard -- +----------------------------+-------------------------------------------+ | Dr. Richard Spitz | INTERNET: spitz@ana.med.uni-muenchen.de | | EDV-Gruppe Anaesthesie | Tel : +49-89-7095-3413 | | Klinikum Grosshadern | FAX : +49-89-7095-8886 | | 81366 Munich, Germany | | +----------------------------+-------------------------------------------+