>>>Now with some serious show-stopper bugs in SP02, it seems that Sedna will be dead as well. My understanding is that Sedna depends on SP02.
>>
>>John Koziol was telling my how Calvin and Aleksey (sp?) could code VFP in their sleep. Well, I know they're good, but my point to him was that they are presently stretched thin, they are not working on VFP as much (meaning they get a little rusty), and they don't have the testing support that they need. How can they turn out their best work in such a situation? I see nothing that makes me want to move to SP2 at the present time.
>
>Depends on the definition of show-stopper - presently only the report bug Cathy found seems to be in that category (from my perspective). If you look at the list of bugs fixed, there are some that can be really troublesome until a workaraound is found, if they inhabit the area you work in. I know from expirience, as one of the bugs I reported meant ballooning file size until Aleksey found a workaround and subsequently fixed it in SP2. Even the SP1 some elevate now so much *introduced* at least one bug - I know for certain, as I for instance reported as one of the first after the release the bug in low-level file handling. And *for me* this bug was in a category even worse as the report bug: not necessarily crashes, but the possibility of totally wrong results. Deadly if you need your data to be correct - but testing flashed it out before trouble was created.
>
>Granted - today SP2 is largely undiscovered country. But that was true of every release shortly after releasing. I *believe* the list of bugs *(re)introduced* with SP2 is less troubling than the list of bugs that were fixed with SP2. If you want to work with vfp at least partly in the next years you should at least know if SP2 creates problems with your app, as this is a "small" release possibly silently being installed by another app on the user's machine. No - I don't send out apps with SP2 currently, all out machines work today off SP1 as default installation. But every machine can access a SP2 install for testing under that release, and at least half of the time we actively work under SP2 hoping to ferret out problems in our apps.
>
>YMMV
>
>thomas

You're right. It depends. If you're heavily exercising the features of VFP that the bugs reside in, you're going to be hurting. Otherwise, SP2 may be a good thing for you. One of my problems with M$ has always been that they refuse to release the bug list. At the point of release, they often know of new bugs that have been introduced, but will not disclose that. Therefore, they make it hard to determine if a move to the new version may cause problems for your app. You just have to figure it out for yourself of keep in close contact with those who make the move and see what their experience is like. So with SP2 . . . here we go again!