Thanks, Jim. One problem, which exists in VFP7, and which prevents several respectful developers to switch to VFP7 and deploy applications, is problem with report writer and complex reports.

So, I'd like somebody to test, if multiple groups (starting from 5 and add group one by one with some summary info) are not producing C0005 error in VFP8. Also I'm curious, if variables, declared in VFP report and set to be released, are really released (I found this problem some time ago and saw it as confirmed bug).

Also, I'm wondering, does Claudio remember, what exactly caused crash at the end of his 3h VFP8 new features demonstration.

>Nadya,
>
>Some have asked about the state of specific bugs in the VFP8 Beta category. Some have been confirmed as 'fixed' while others are noted as not fixed.
>
>Perhaps if you asked there, supplying sufficient information to let people with the beta in hand test them, you might be able to learn if they are fixed in VFP8. Surely any that are fixed would be good news.
>
>
>>Thanks, that's what I expected, but needed another confirmation.
>>
>>Well, it's too bad. The Report problem seems to be very serious. I have a discussion going on in Russian VFP Club about this problem. Apparently, Russian developers still are hoping for new SP.
>>
>>>See Re: Visual FoxPro News Flash Thread #647154 Message #650072.
>>>
>>>>Hi everybody,
>>>>
>>>>Do you know, if any bugs fixes are expected for VFP7? In particular, two problems seem to be most annoying:
>>>>
>>>>1) Flaws in VFP Report Designer - if report is complex, you would have C0005 error almost predictable (same reports work fine in VFP6).
>>>>
>>>>2) Intelligence error. When you type thisform.myMethod() you often get a C0005 error (it could be fixed by running VFPClean for the next occurrance of the same error).
>>>>
>>>>Thanks in advance.