Hi John,

>You mean as far as .Net is concerned?

Not necessarily... all I know about .net is that vfp is not part of that plan and at my level I can't even wonder if that is something that can or cannot be fixed/patched. But even if vfp has no part in the .net revolution, I think real change is about a year away at this point.

>
>VFP is not a player in that space. MS is certainly not pushing it as a tool for that space.

LOL! That's the understatement of the year! MS is not pushing it, period!!!!

>Sure there re aspects of VFP that can fit into that space, but that is another issue entirely.

Well, I certainly see a seed there. If not for any other reason, just because someone familiar with the whole mish-mash is saying it. You just qualified yourself as our first volunteer ;-)

>With that in mind, why would MSDN print pieces that deal with VFP integration into .Net? The targeted audience is too small. From a page allocation standpoint, it does not warrant the space..

Right again... would be pitiful if we have to _buy_ space in the magazine in order to promote the product... I'm sure something can be done about the page allocation issue. I've seen weirder things happen before.

>Not trying to be "mean" or "cruel" here. Just trying to be objective...

Your points were well taken...

Alex

>
>
><<
>I don't mean to be rude or negative, but with all the talent that lives here, wouldn't it make more sense to submit a couple of articles to the magazine than to make sarcastic comments about the word "FoxPro" appearing twice in the latest issue?
><<