>Um, Erik, do you mean FoxFire! wasn't rewritten for VFP 6.0? Because I definately have a 5.0 and 3.0 version... Or do you mean that it doesn't take advantage of some particular element of VFP? Also, what are you going to move to from FoxFire! (if you don't mind my asking*s*).
>
>Thanks.
>
>>I have seen this happen in my apps with Foxfire!. I cannot explain why, or how to prevent it, but I have tracked down one occurence to a RESTORE FROM MEMVAR in a tight loop in the Foxfire! source. The inconsistency of the problem leads me to agree with Nancy, that it is not necessarily a Foxfire! problem, but more like a VFP problem that gets highlighted by Foxfire's code.
>>
>>I will be moving away from Foxfire as soon as I can because of precisely these types of errors. I think the fact that the product was not rewritten for VFP does not bode well for its future.

There is a OOP style report writer out now, called bullseye.. I have just d/l'd their demo and will be playing with it.. Sounds good so far, maybe they will replace FoxFire! as the new Report Writer for VFP??