Hi Tamar:

>Microsoft has announced no plans for a service pack and, in fact, when VFP 8 was released, indicated that it had no such plans at that time.

I bought VFP7 at the earliest possible time. Whilst I should have checked my code, I upgraded a couple of automation project to VFP7. The code broke in VFP7 - I reported it to MS and they acknowledged it as a bug. When SP1 arrived, it still wasn't fixed but there was a workaround. However, the code ran perfectly in VFP6.

Looking at VFP8, I would very much like to upgrade to it but after my experiences with VFP7, irrespective of whether MS announced no plans for a SP, I will definately hold of upgrading until a SP is available. Many claim that VFP8 is the most stable version of VFP ever. Whilst that may be true, I am definately noticing the bug count rise. The bugs may not cause crashes but there still seems to be a steady stream of them emerging as reported on numerous forums.

I notice over on the WWWC board, Randy Pearson has repro'd a serious bug with the collection class. He has found problems using object references via FOR EACH (this was a similar problem with my automation bug in VFP7). His answer ... use FOR i = 1 to collection.count. For a much touted feature where one of the advantages was being able to process the collection with a FOR EACH, to find this is buggy is a bit of a poor show.

We'll see.

Best