Hola Tocayo,

I think you're ready to try your luck with a framework. This way you will be somewhat "forced" into thinking oopishly and at the same time make a move into a multi-tier paradigm smoother.

If you're dealing with a lot of globals, you might want to convert those into properties of your oApp class.

You should start spending some time looking for a framework that makes you comfortable. They all have money-back guarantees, so you should try at least 2 before deciding which way you want to go.

If money is a very important consideration, there's one framework that's freeware (codebook), but given that there isn't much support for it here (CB users have their own forum at codebook.leafe.com), you probably should start there.

I started by looking into the pseudo-framework that ships with vfp. Pseudo because there's almost no documentation on how to implement things, then I looked into codebook, which confused me incredibly (I was VERY new at VFP and OOP at the time), then I tried Promatrix, which didn't quite integrate with the way I work, and now I'm using Mere Mortals (which is based on Codebook).

I'm having my problems here and there, but aside from the normal learning curve to anything new, I'm getting by and am quite happy with my decision.

If you feel more comfortable talking these things in spanish, mandame un email y te ayudo en lo que pueda.

Good luck!

Alex


>Hi,
>
>I have a large app that I am moving to VFP. I have been doing things in a very non OOP way.
>
>Frequently used routines reside in the start up program, in a procedure file, or in separate files if they are large. Setup code for reports resides right in menu snippets. There are also a lot of calculation routines in the procedure section of the forms that need those calculations.
>
>Lastly, I use global variables to hold some frequently used values that I do not wish to fish repeatedly from the parameter table.
>
>I wish to follow good OOP practice. A friend suggested three main objects: oApp, oBiz, and oDS (for data services). While these are good classifications those objects will quickly become bloated and it will be hard to find things.
>
>I am thinking of adding the following objects:
>
>1) oCalc. To hold calculation methods. One method, for example, may calculate accrued vacation.
>
>2) oReports. Its methods would setup reports as well as call the report itself.
>
>3) oValues or something like that to hold a bunch of values that I need quick access to. These are awfully much like global variables, but at least they are loaded upon object instantiation and therefore are more standalone.
>
>What are natural subcategories that people use ?
>
>TIA,
>
>Alex