>The only thing I can say is never change for the sake of change.
>
>If things work fine for you, stick with it. Yes, there are advantages to VCX based classes - and disadvantages. You need to weigh the pros can cons and act
>accordingly.

I agree. And I think that when it is an advantage to use one method, use that method. When it is an advantage to use another method, use that method. I think going to any extreme (ie. I never... OR I always...) can be inefficient.

John Burton, I would suggest trying the Form Designer before making the decision to NEVER use it. If you try it and can't use it to be more productive, then stick with coded forms. But to make a decision without all the facts/experience might not give you the best result.

Just my opinion,
Joe