Hi John

I have to take issue with some of your points.

You seem to be under the impression that VFP people only know VFP. This has not been my experience. Anyone, regardless of what the code in, suffers if he or she only understands one tool. This is granted. In my case, personally, I know enough VB to hack away where need be and have a pretty good grounding in SQL Server.

Now...if I'm to believe some MS documentation, I already have an enterprise solution marrying VFP to SQL Server. If VFP is everything that the Fox team at MS tells me it is, then I have good cause to scream bloody murder when an ActiveX control doesn't work. And...I might add....there is little or no documentation from MS that specifically tells me that VB is used here and VFP is used there. In fact, the one paper I did read that was a comparison of VFP to VB to Access ended up by saying that all things being equal, go with what you know.

By saying not to expect ActiveX support or other features is like telling me not to expect my trunk door to work on my Chevy because Chevy is not GMs favorite car and I should have bought a Pontiac. Nonsense. If VFP has a UI I expect it to work. I don't buy this VFP is middle-ware and little else....I didn't buy the car for the engine. The trunk door, dome light, and tachometer better damn well work and work well.

Most VB developers I know wouldn't know a foreign key, for example, if it bit them in the ass. Talk about blinders. Most professional VFP developers understand the bigger picture, IMHO, far better than VB developers who are far more closeted and professionally short-sighted.

As to the MCP issue: I, for one, am looking at the bigger picture with the new MCSD track. VI,VJ and SQL Server people are getting kiboshed. Again, in my experience, Java and SQL Server people are much more heads up in solution development than VB people. Yet, VB (and VC) developers are given the inside track to certification and they don't even have to prove they understand Windows Architecture anymore. Does this make sense? MS is really screwing the pooch here, making things easier for VB programmers and harder for developers with arguably stronger architectural and big-picture skills.

I think you're selling VFP people short and I think you're giving way to much credit to the VB dittoheads.