I think your use of the Telephone industry is perfect for this discussion. Some experts are now predicting a major revolution in the telephone industry as VOIP becomes more popular. Of course not all homes have broadband. But as the installed base of VOIP becomes larger, the phone industry as it now exists will have to change.


>>>The Fox community has got to have the biggest collection fo folks that do the same things today they did 15 years ago....
>
>If you are correct... so what? If it is good business, why go through the turmoil of changing it around just because people whose own business depends on "coolness" (your word) or "experts" that rely on new technology to create expertise opportunities for themselves, are promoting something different?
>
>Look at the POTS telephone industry. Not exactly a mom-and-pop... but it relies on truly ancient technology in many aspects, including loops installed decades ago. There is absolutely nothing wrong with that. A smart business upgrades when it makes BUSINESS sense, not just because something cool and exciting is being promoted by people who make $ if they can convince you to upgrade.
>
>In any case, it is perfectly clear that most here have several strings to their bows, including some VFP stuff, some dotNET, maybe some Linux and/or Java. The caricature of the "VFP-guy" as a blinkered one-horse wagon stumbling towards a cliff, is disparaging and distracts from whatever point you may wish to make.
>
>My opinion is that many of those happiest with FP are not "luddites" at all, but those who were the earliest adopters of C/S and web interfaces, and who therefore may not perceive the UI or scalability advantages of newer offerings as killer reasons to move. We released our first SQL Server app in 1995 and have found it difficult to say "wow" when people have extolled the virtues of other offerings whose advantages generally boil down to SQL Server attributes that we have taken for granted for years.
>
>Just to head you off: in my case, we use dotNET for a UI for customers and for importing HL7 documents to a repository. these are then submitted via XML to a VFP server app that does all the hard work and sends it back. I suppose we could do the server in dotNET but perceive absolutely no business advantage in that huge expense. I think the system will serve its natural life in this configuration, and I'm sure you would regard it as good business were you in my shoes. However, I offer this as an example not as a "proof" that my particular circumstances should be followed uncritically by everybody else or they are -insert disparaging epithet here-. You might like to think about that.