Absolutely. One really must remember that everything has its own place and purpose. Event-driven models, forced to sit behind/in a gui framework, just do not fit transactional processing. Remember, transactional processing is back-office, streams of items in, process, filter, archive, and out - stuff that procedural languages COBOL/PLI/ALGOL/FORTRAN/C - can do extremely well and concisely - all with little fluff, transfer vectors for each instantiation, etc., etc. Sometimes it is appropriate to apply structure, abstraction, dynamic binding, etc, to transactional processing - implementable readily in C (and even COBOL with a little preprocessing) - but that is only structure and expression. That does not make COBOL any more appropriate for events driven by HUMAN interaction, nor C++/Net appropriate for transactions. chrysg