I guess we have different opinions about this <s>.

What is the downside of having multiple files? There certainly is less overhead in that than having multiple records in a VCX file for instance.

To see problems with multiple files in the same editor, try putting two forms in the same file and then edit them through the visual editor.

Keep in mind that even individual control classes can end up fairly large. Just fixing the DataGrid control to a point where it is usable is fairly lengthy for instance.

Regards,
Markus



>>I think the piece of technical advice about classes and individual files is particularly relevant to VFP developers for the reasons you state. <
>
>Well, I gotta disagree with Markus on this one and since his blog doesn't allow replies, I guess I'll have to say it here. <g> Yeah, I know he mentions that there are exceptions to this "rule", but he doesn't even mention the exception for your base control sub-classes (like your TextBox, ComboBox, etc.). These really should all be in one file. Can you imagine having a separate file for each of these base controls? That's definitely overkill, IMHO.
>
>There's no problem with the VS.NET editor handling multiple classes in one file, I'm not sure why Markus said that's a problem.
>
>Bottom line ... I don't think that this should be a hard and fast rule.
>
>~~Bonnie