Why quick and dirty ?

Having most of code in Prg code doesent mean abandoning good OOP
principles / practices. Not at all.

You can always call forms from within prg code to perform user GUI,
while GUI can also call back obect methods in PRG to perform data
processing and so for...

Have nice GUI for your users while still keeping most of code in powerfull (prg) underworld :)

Rgds++

>>Personally, I find prg's much easier to maintain, then code scattered all over bunch of forms and classes objects in vcx libraries.
>
>Precisely that was why I was interested. I could do things quick and dirty in code but when it comes to layout I could use the GUI.
>
>Pity <g> there is no GUI for prgs except for modi comm.