Re: changying from ANSI mode to unbuffered logging

> Yes, that what we are going to do. Recreate the database. If there are any > other ways please advise. > > But, the application developers worried that something might not work if we > changed. Any idea?? We have 4GL, stored procedures, and client PowerBuilder > applications. I assume you're aware that unbuffered logging requires explicit BEGIN WORK statements to denote the start of a transaction? ANSI logging assumes a BEGIN WORK and requires a COMMIT WORK or ROLLBACK WORK to terminate a transaction, but unbuffered logging will allow your programs to perform DML statements outside the bounds of a transaction. Actually, each statement is considered a separate transaction if there has been no BEGIN WORK. This could cause a big problem if your programs try to do a ROLLBACK WORK. Mark Collins mcollins@us.dhl.com The truth shall set you free, but a good lie will keep you out of jail in the first place.