>
>I was aware that there were issues with composite classes. I have the Advisor issue and I will read the article. I note that the article relates to 5.0/3.0 & Fox 2.x. I don't suppose that 6.0 makes his comments moot?
>

Not that much has changed from 5 to 6, although there were a number of bug fixes. I can't specifically if the things Drew talks about are still there or not, but I'm pretty sure most of it hasn't changed.

>
>Another consideration is that we intend to have non-programmers build many of the UI forms, with a programmer coming in after to hook up control sources and write any additional validation code or what ever needs to be done.
>

Yikes! What a scary thought! Really, though, having non-programmers deal with the UI of the VFP development environment isn't going to work, unless they are really sophisticated. I think dealing with the complexity of the class structure you're talking about is enough to baffle them, even if they are sophisticated. It's probably better to create fewer, generic classes, and have you go in after the fact to set specific properites or send the needed parameters in code.