>>embolded hints at need of heavy KISSing in your hobby projects...
>
>The component involved (two vcxes and perhaps a dozen prgs) were borrowed from my old homemade framework (one folder) and a project I did 17 years ago (another folder) and, this being a hobby project, I didn't bother to separate them. It's more a matter of entanglement, inherent to vcxes in general, when adding just one class into a project pulls the whole inheritance tree for anything that's mentioned anywhere in the vcx. I had cases where disentangling for a project took three days and resulted in the exe trimming from 2,5M to 54K.

vcx entanglement is one of the reasons for my decision to only put purely visual stuff in vcx. Mikes rule of 1 function, 1 Prg is still too harsh for my taste - my rule is 1 prg for up to a handful of classes (more dependant on the # of methods visible in document view: 1-3 screens is ok, more a hint to break up.)

>I think I'll just give up on the grid and build a container with controls as required, then add containers for each record. I don't really need scrolling, header and ot grid stuff.

Hmmm, cursor is the basic sauce of vfp and grid the visual cousin...

>p.s. a funny artefact of the grid: the string column was V(127), and as I clicked on different rows, all other rows would display longer or shorter, in the length of the current row. Had to make it C(127) and trim the result when writing back into the ini file.

Not wart free, but still...