It may happen, but as exception only. This is supply-driven software world. Some 'minor' OS/MTS/somethingS version and all they got rewritten regardless how well they were built. I don't speak as technical person now.

>I guess what I'm saying is that I do see some modern business objects, if built well, surviving for 10 years + if they work and play well with others *and* the business rules they encompass don't change.
>
>>Obviously, I did not mean mainframe, that's another world. But in PC, these times it changes much quicker than even in FoxBase days. It's encouraging to hear about successful moving FoxBase to VFP and preserving old code, but let be honest, it's not the mainstream way. Also, FoxBase did not have business objects, eh :-).
>>
>>>Hi Ed ----
>>>
>>>Interesting that you bring this up. I know that business processes and some code (although not, technically, objects) do survive for 10 years and even longer. A financial application I wrote in 1987-8 in FB+ was rewritten a few years ago in VFP. Rather than toss out business logic I had in procedure files, the developers hooked into them from the UI.
>>>
>>>I am currently involved in a project where an old mainframe system is being redone...and they are going to keep and call most of the old CICS/COBOL procedures because they represent the best practices.
>>>
>>>
>>>>Do you believe in 10 years old business objects/data/application/whatever? The real life span for a business objects is 2-3 years at best, and even less when another developer jumps in :-).