>Are we supposed to modify some of these ffc classes? when I use the oldini one it always returns a constant 0. thats the code, when i modify it to RETURN m.cValue its correct. So are we supposed to change it or did MS forget a step?

(1) There have been updates to many of the FFC classes available on msdn.microsoft.com/vfoxpro/downloads for a while; these were incorporated in SP3 I think. I don't use the FFC Registry class, so I don't know if it was broken, or if it's been fixed, or if it was fixed, if it was fixed before SP3. If you don't have SP3 installed, I'd try downloading that and applying it before modifying the FFC myself.

(2) There's a reason they give us full source code to the FFC, and it isn't just to take up space on the CD. If you don't like how it works, make it work yourself, either by fixing it in the FFC itself, or better, by altering the first-level subclass of the FFC (you are using a first-level subclass and not the base class itself, right?)

(3) The registry classes available for download here on UT still work. If the FFC doesn't meet your needs, you do have alternatives freely available to you here, and on other VFP Web sites.