>>I think that in your case, by tearing the existing FFC stuff apart you've done yout time learning and that is what will pay off in the long run. I want a framework I can easily (relatively speaking) retool for my own needs. For some odd reason I always seem to want them to do something they weren't intended, hence my desire for one like the one I'm currently going to be checking out.
>>
>
>It was definately a learning experience. I learned that writing a framework is not the first thing you should try to write when learning VFP ;)

Roi,

Cripes, it's not something us old horses particuularly want to do either! *rof'l*

It's just that, to me, an effective framework is one you never know is there, if you get my drift.

It's kind of a sad truth in our industry that the really really good people and work should never be noticed. IOW, I know things are going well when I don't have a line outside my door complaining about this or that or wanting some enhancement. The problem is that you achieve that by good deliverables, not by being so cranky that people don't want to talk with you. *g*

The result is that all we emotionally startved developers occassionally get together and cry in our beer (figurative or more likely literal *g*) and whine about how unappreciated we are. Of course, when we submit our time shhets or bills we do ..er.. gain a certain amount of satisfaction....

Best,

DD