>We simply do not communicate very well together, George, so I'll leave things where they are. Suffice to say that the KB article is actually next to useless and doesn't state that it is still a problem in VFP7.
>I still cannot 'get' the idea that the VFP Team doesn't know what fixes they've implemented **before** the public actually obtains the final product!

I think that we don't communicate very either, Jim. However, I think that from your statements, you really don't understand what's going on here. You keep referring to the "VFP Team" which, if I understand correctly, you think is also responsible for updating the KB. Now if I'm wrong here, I apologize, and you can disregard the rest of this message. If I'm correct, however, here's the scoop.

The "VFP Team" is most certainly not responsible for updating the KB. As I understand it, that's the job of Product Support, which, BTW, covers all products. Now if I'm incorrect in this, I'll trust Garrett Fitzgerald, who works for Product Support, to step in and correct this and what follows.

Product Support is responsible for writing, editing, reviewing and updating the KB articles. The articles are reviewed periodically, and given that there are literally thousands of articles to review, it's not terribly surprising that those covering VFP haven't as yet been updated. As a point of fact, it sometimes takes weeks, if not months, just to get a new KB article in there.