>There is stuff that is not wise to have in classes. And instantiating odd objects with each and any form just to use a single method is a lot of overhead compared with a procedure. Global classes solve not any problem, because the run in different DATAENVIRONMENTS. Procedures run in the one calling.
>The purist OOP-only days are over - if you are happy with your procedures, use it. The only downside I see is that, the visual interface to edit methods is much nicer then scrolling through huge PRG's. (Don't get me started on 32605 lines of FoxBin2PRg.prg ...)


32605 lines? It's a small prg file.


MartinaJ