>Hello to everybody,
>
>I want an ultimate comment to buy a Framework, based on your experiece working with frameworks. I never had worked with a framework, but due to not enought time to develope and reprogram a complete application I am thinking about buy a good framework, in my case I have to migrate and reprogram an accounting system and inventory system, but using SQL for the backend, then I have to complete that project in a very little time.
>
>I will apreciate very much your valuable comment about that. I was viewing Mere Mortals and Visual Promatrix Frameworks, superficially are very good but i wish a little suggestion about it.

I was working with Promatrix (5.1a to 6.0b) for two years and I'm actually glad it's over. Didn't check the Enterprise version, because they said it needs your app to be based on views, and we had lots of stuff done in VPM5.x which didn't know how to handle views, and they didn't seem to offer any transition tool.

About quarter of my working hours was dedicated to, "fine tuning" of VPM. It had too many refreshes, too many things were based on macros being expanded each time you use a feature etc etc. By version 6 it still had a zillion public variables, and these were supposedly replaced with oapp.properties, but I didn't really want to hunt down all the places where we referenced these publics in our legacy code. Also, too much code was in .scx, .mnx and .prg files which were copied for each individual app (i.e. not classed), and copied over with each upgrade, and the error handler was a special beast which first closed all your tables and then tried to resume running your code... which led to some 60+ clicks before I lost patience and killed the task.

Summary: it's nice and quick to begin with, and you can do a lot really fast. If you don't come up with good internal standard on how to use it, you may create yourself trouble in later maintenance.