>But my gripe is broader - look at last months UT Mag - NET - NET _ NET _ SQl - SQL - SQL - nTier - nTier - nTier - I can see my self trying to convince a 5 node user that "we need to get SQL and spend lots of time writting geeky n-Tier objects"

Oh, no! That's not fair, Terry. 8-)

We have being publishing lots of VFP stuff. The fact is that the magazine is not *just* VFP, as it have never being. Indeed, it always reflects the interest trends of the community. I can understand that many people are not interested in .NET, as you, but you can deny that there is a lot of interest out there, and indeed, we are one of the few sources for learning it from a certain VFP pespective.

We are not even forgetting about older VFP versions. In the last two issues, we published articles about performing some of the new VFP 8 features in earlier versions, like Try/Catch and Collection classes, and more are coming.

But, again, as it has already being said but people a lot more trustworthy than me, like Jim Booth, for example, every application can benefit from a tiered architecture, no matter its size.

Finally, it's not true that you have to "spend lots of time writting geeky n-Tier objects". Once you have your framework architected that way, you can develop as quickly as with any well-written framework. But using n-tier, you have many advantages, like flexibility, better quality control posibilities, and many more.

I really recommend you to read some of our articles on the topic and see what's this about. It's not something that have to add complexity, but actually make things easier to develop and mantain.

Best regards,