Jim,

Well, look.. I think we all agree that VFP should be as 'tight' as possible. I think we all agree that in the real world more than likely there will continue to be issues with bugs, given that ther really is no such thing as perfect software - or really much of anything else for that matter. <g>

So, I guess for me it kind of boils down to three issues:

1) Are the developers of VFP fixing these bugs as soon as they are able? IOW, do they care and do they have the intrinsic talent to respond? Have they so done in the past?

Answer: Resounding YES! YES! & YES!

2) Is the product, in its current incarnation, able to allow me to provide my customers with a solid product? IOW, am I able to code around known bugs?

Answer: YES ans YES. Now, I'm willing to cede that I would like to have that list of bugs. I also understand why Microsoft's corporate policy precludes the VFP team from posting them. I candidly think that the VFP team would be more than happy to post the information (all of us at the same time acknowledging what a huge task it is to track them) for all but their hands are tied. Here you're just preaching to the choir and IMO that seems to me to be wasted effort. Why not write the company? Perhaps there are issues (legal?) that Microsoft's lawyers are concerned about that is the real reason their not posted. For companies like MSFT there must be tremendous landmines they need to avoid.

Since you've gone to the trouble of gathering them why don't you post them in such a fashion that the community can turn to that list for help? Sounds like you're headed for UT MVP territory! <g> I'd appreciate it.

3) Are the chances any good that Microsoft will change their policies in this regard?

Answer: More than likely NO.


Since I am able to compensate and am not prevented from so doing I think that the issue is somewhat moot. I just think we've beat this issue to death and are right where we started.


>snip<