You can have your options:

- The Microsoft way: Issue Hot Fixes when needed, then incorporate them into a Service Pack. Each Service Pack has all the fixes from the previous ones.

- The Novell way: You must apply each Service Pack and/or hot fix in the proper order. This means download and keep track of lots of files and go through detailed installation step by step.

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.


>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