Informix and GUI's

I have some sort of "How To" questions regarding Informix and GUI programming. The toolset isn't really important here, its more conceptual. One of the behaviors of typical GUI programs is to have some sort of main window, and then have the ability to pop-up other, smaller windows at whim. Now, one may want to be able to manipulate the data in these pop-ups (change/insert/delete data). However, in theory, there is no real reason for these windows to be modal -- they should be able to just linger as things change on the main screen. The problem is that they should have a seperate link to the database. You wouldn't want to have that little pop-up be in the same transaction as the main form. Does ESQL/C allow one program to have different "connections" to the database, each with their own transaction? How about the Windows front-ends coming in through I-NET? I was always under the impression that the sqlexec managed the interaction with the transaction, and 4GL doesn't have any mention of being able to have seperate transactions. When a session fires off via I-NET, does sqlexecd fork an independant sqlexec to handle the session? And if Informix allows multiple connections, does each one get an sqlexec? Isn't that a little expensive? If Informix DOESN'T allow this, how are you folks writing GUI applications? Are your apps basically a horribly modal scenario with one main screen and lots of modal dialog boxes? A character app in a cheap, plastic box? Or do you just turn off logging, and handle transactions on your own? Thanx for any info you may have. Will (la4gen!villy@uunet.uu.net)