Re: Multi Tiered ODBC

I have seen a company choke bad on multi-tier architecture by putting too much logic at the bottom client level. The user interface client is then not able to be replaced or easily maintained. A complex PowerBlower client (dead beef) cannot be easily ported to Java (latest cool thang.) The software release of builds between the many platforms of servers and clients was a major downtime nightmare, coordinating the PC code, Unix C, database, tuxedo, dinosaur code, etc, is still a problem. I favor a simpler client for GUI with business roolz in the server level for data entry type applications. The GUI client can then be replaced by whatever (X,java,windoze) much easier. The technical level of the IS organization is also a factor. Hiring a bunch of high buck consultants (like me) to write a multi-tier architectural application, only to have the 'experts' split the company a few months later will make for some expensive problems as JOES ROCK CRUSHER, Ltd tries to maintain and administer a complex application with a few computer operators and heavy equipment mechanics. Good luck pal.