>There you go again, taking an argument to a ridiculous extreme. :-)

Thats me :-)

>You're the one talking about obsolete languages or components, not me.

I know. I'm just taking into consideration the value and lifetime of the flexibility gained by the requirements and limitations of building an n-Tier app.

>I didn't say you can't reuse any code, just that a well-designed n-tier app leaves you with lots more options for rewriting PARTS of it as needed (if needed) without starting over from scratch.

And I'm saying exactly what John replied to you with, unless there is no short term or mid term requirement for that need, chances are when its time to scale or flex the app, a modern rewrite will be more productive then dealing with several outdated/unsupported technologies and trying to get them work. Could you imagine trying to support a solution of a VB3.0 app and a FPW app that used DDE and a Sybase backend today? It may sound silly, but someday, we'll look at teh VB/ASP/SQL solution and thikn that was very strange too.

>Personally, I expect to be using my VFP code for many, many years to come.

If MS up and dies in 5 years, will your extremely flexible Windows DNA apps be so flexible we you need to throw in a Java and Orcale solution?

I'm not saying n-Tier is bad, its cool, I like it. I'm just saying you don't always need it, and it won't be the final paradigm we use.