Better take a look at the November issue of the Visual Basic programmers journal.

>After reading the MS ignores VFP thread I had to write.
>
>SET SPEW ON
>
>If, as a VFP developer, you want the Fox community to grow, you must take it to th VB community. Don't wait for the magazines or MS to do it. They won't. MS has made its decision regarding VFP vs VB and we lost. The magazines will only do what sells more mags and ad space. It's also not the mags job.
>
>Our user group recently expanded to add more MS tools. I personally have worked with more tools than ever before. Working together with the VB/Access/Delphi/PB/C++ people we can show the strengths of each others tools. I don't buy the agrument that Access & VB have nothing to offer. There are too many people making a lot of money off them.
>
>Here's some things *you* can do.
>
>1. Join a user group. You may be the greenest programmer in the world and you still have something to offer.
>
>2. Find someone who is as rapid about there product as you are about VFP. Ask them to show you the benefits and cool things. Only show VFP if they ask. They probably will.
>
>3. Get on a project using another tool. Learn the other tool. When a really difficult problem pops up, see if can be used to solve that one problem. Don't push it after the problem is solved. They'll eventually come to you after VFP fixes enough propblems. Oh, you'll also have another tool you can use to earn a living.
>
>4. Don't bad mouth their tool. The first person I tune out is the guy who thinks VFP is "dead, lacking, xbase, old." They'll do the same to you.
>
>5. Write and article for some other magazine besides VFP advisor. If you want it in VB Programmer's Journal (which is a great mag, BTW), show how Fox & VB/VBA can be used together.
>
>Last but not least - STOP WHINING.
>
>SET SPEW OFF
>
>Thank you for your time.