> >We've never had problems with Kaspersky and VFP (development environment and runtime).
> What versions of Kaspersky and VFP are you using?
> How often do you modify reports with the report designer?
> Del
I'm currently running v7.0 of Kaspersky on my computer. Most of the computers here at the office are running the same version of Kaspersky. There are a few computers that are running other antivirus software like BitDefender, AVG and Avira (just replaced the last instance of Norton Antivirus last month). Never had any problems (except for Norton Antivirus, which tended to eat up machine resources -- with which there was typically a 10%~20% load *minimum*, with occasional spikes of 60% -- while the machine was *idle*. After replacing with Kaspersky the loads dropped down to at most 5% load while idle). I'm usually working off the network drive, and never had any problems. I'm working with VFP 9.0 (for new projects) as well as VFP 6.0 (maintaining some older code), and occasionally having to drop back to use FPW 2.6 (again to maintain some older code).

Never really had any serious problems with the report designer, although I've adopted a practice that works around an old bug that was in FPW 2.6 (which isn't the problem you've been having). In FPW 2.6 if you continue to edit a report after adding/removing groups, you ran the risk of objects ending up in weird positions (despite the screen showing the updated positions of the bands, the report designer behaves as if the old band positions are in effect, so resizing the bands or moving the controls results in odd positionings -- which you don't see until you re-open the form). What I usually end up doing (to work around this problem) is to simply save the report immediately after changing the group information, close then re-open the report. Since adopting that procedure I've never encountered that old bug (because I'm simply working around the situation that gives rise to the bug). Haven't checked to see if VFP has the same problem or not (and since I find myself dropping back to FPW, I've just simply made it a matter of habbit to avoid the problem altogether by working as if the bug still occurs in VFP). The other old FPW bug with report designer that I've had to contend with is the incorrect updating of the reset condition for fields that get calculated after adding/removing groupings (this happens if you add or remove groups and have headers and footers that are blank).