>I have programmed a fairly large application, and chosen the FFC framework, which I now totally regret.
>
>The application is becoming more and more unstable, C000005's galore, which I attribute to an excessive use of the TYPE( function where the framework checks all over the place the TYPE( of all sorts of objects and properties, many of them don't even exist.
>
>We don't use that much of the framework, the standard toolbar to invoke forms, add and delete records, the navigation toolbar, to go from one record to the next etc.
>
>What are our best choices now?
>

If you haven't done so yet, download and apply VS SP3; it fixes a large number of memory management problems that manifested themselves as C5 errors and added some new features as well. You can download it from msdn.microsoft.com/vfoxpro/downloads/updates

>1. Try to get rid of the framework altogether (any suggestions on how to do that)
>2. Modify the FFC?
>3. Go to another framework (is there a framework that makes it relatively possible to migrate to it from FFC?)
>4. Hire an expert in "FoxPRO framework salvation", what are your rates? There are about 40 forms in the application.
>

You might want to buy Marcus Egger's book on Advanced OOP in VFP6; he covers the FFC in some detail

>Thanks in advance for any advice.
>Hermann Strijewski,
>Clearwater, FL