I think that Micromega is aware of our sentiment, and the choice to not rewrite was a conscious one. The way I figure, Foxfire just did not fit into their future business strategy. Andy MacNeil, one of their key developers left and has since written an object development kit for Foxfire, but I have not checked it out.

See my response to Nancy about future plans.

>Thanks Erik for the info. May I know which Report Writer you are switching to? I totally agree with you on FoxFire's stand. Without rewrite developers like both of us just feel uneasy.... I hope they take note on this.
>
>Regards,
>Farouk Yew Abdullah
>
>>>This is no help, but I see the same thing happening daily in my VFP app. So, I think it's not related to FoxFire! per se.
>>>
>>>...snip
>>>>VFP caused an invalid page faults in module KERNEL32.DLL at ....... etc.
>>>...snip
>>
>>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.