>Personally Tom, I think you are being too forgiving.
>
>This is situation is unacceptable and can only be truly rectified by a recall to the retailers.
>
>But as well all know, this is not going to happen. As a result, it makes everybody look bad.
>
>I'm passing this bug info onto a friend at Dell. I'm interested to know what their take on it will be with their VFP7 bundling offer. If I am permitted, I'll post his comments here.
>
>
>>Glad VFP 7.0 is available for download. We all know that software is never complete or “anomaly” free. This is a product that has been anxiously waited for and now it is here!
>>
>>I congratulate the Microsoft staff for it’s fine work. At the same time I have mixed emotions about the “hot fix” issued yesterday. This is certainly a “heads up” from Microsoft and shows they are on top of issues that concern us. At the same time I am concerned that the retail version will not have the fixes. I just hate to see VFP 7.0 “go out the door” with known problems. This is a difficult position IMO for Microsoft but this is the world of software development.
>>
>>Somehow I feel if the product is released to the retail market with problems of this type it will be viewed as a less than professional product. We have enough of that concept to overcome within the IT world. This could just be more “egg on face syndrome” for developers.
>>
>>Tom

Jeff;

I like Craig’s comment: “Having been testing VFP7 for many months, I doubt additional testing would have caught this bug. My guess is that the bug wasn't found until a VFP7 app was deployed.”

From the Microsoft web site: “A known issue with the Visual FoxPro 7.0 run-time libraries prevents an EditBox control on a form from displaying its scrollbar. An EditBox control will still allow scrolling using the keyboard or the mouse. This issue does not occur when forms that contain EditBox controls are run under the full development version of Visual FoxPro (VFP7.exe), and the issue applies only to runtimes that ship with the English product.” Now to be honest there are seven defined “Late Breaking Known Issues” and I have just addressed one.

From these two statements which seem to agree with each other I can conclude the following: No one created an exe and tested on a clean machine until the last day or two. Seems like this product has been around long enough for someone to have thought of that. It does not surprise me though as I see all too many testing environments actually being done on a developers machine. Will every user of VFP 7.0 applications have VFP 7.0 installed?

Another thing that is a “kick” is that it “applies only to runtimes that ship with the English product.” Glad to know that as it means this problem (and the other six listed issues?) are limited to only the English product!

Tom