>Hi for All,
>Someone could me help with any information about :
>
>How to design a Persistent Object Framework with VFP?
>
>Thank You for Any Help
>and Happy NEW YEAR

Hi Eduardo,

You'll find many answers to that question if you think about alternate nomenclatures and ways of decomposing the problem. I can't give you a simple answer, but I think the central issue is to devise a general system of state saving and restoration. Also, it may simplify matters (and achieve greater generality) to separate the mechanism for "persistence", from the details of your "object framework".

FoxPro itself, for example, uses a "resource file" to save and restore the configurations of browse windows and other system windows, and the FoxPro Foundation Classes (FFC) include a rudimentary Object State class to save and/or restore object property settings automatically or explicitly. A popular practice originally encouraged by Microsoft (but which I'd never recommend), is to record object state information in the Windows registry, and another widely-used (but hardly general) approach entails the use application-specific INI files, and the like.

My personal opinion is that there exists no better tool than Visual FoxPro for building such systems, because the problem plays into VFP's unique combination of strengths: tight database integration (for convenient, efficient manipulation of metadata), dynamic power (for table-driven architecture), and OOP design (for modularity, reusability, extensibility, maintainability, etc.)

Good luck on your project, and best wishes for 2004!

Mike