So it seems there are not only germans in the ivory tower. This is one of the main reasons for me to start developemnt with vfp: I will build a database level approximation FIRST and simulate needed processes on that level with a few browses. IMHO much better than working from an object model through automatic ORB's to the backend level. Most of the time I can pinpoint bottleneck points working in vfp bae tables make sure performance is still ok under C/S rules by switching over to cursoradapter. Adding biz rules and a GUI won't land you in trouble if afterwards you adhere to "chunky not chatty" when implementing functionality in the other tiers.

The thing bothering me most when working in java is that often I am quickly sent into the ivory tower when they see I have an implementation working fine with only a minimum of the golden rules broken (as a counterweight to change dumb "golden rules"). There I am the one eyed man in the land of the blind, which does not help at all when the job of king is determined by other factors<bg>. Hope you have better luck in your new job and/or are a better coporate team player than me.

>Where i'm at now there's a separate architect dept. I've actually heard these bozos say they don't need to understand the business processes to create a good data model. On the last 2 accting systems i've worked on, they have surrogate keys in the account code table. So the surrogate key is also in the transaction table. Similar in some other code tables.
>
>This means that any report needs at a minimum 5 or 6 joins. And there's not always proper indexes. So they can't figure out why reports run so slow. In another sub-system some of these same people normalized the data to such an extent that some what you would think of as simple inserts, need to update 8-10 tables.
>
>They actually paid MS big bucks to send in some experts to tell the company why the system was so slow. If an insert required updating 8-10 tables, reporting was extremely hairy. When they first went live, if 2 people ran the wrong reports at the same time, it locked up the entire system.
>