>Another thing we're seeing is a proliferation of incompatable controls (mainly
>from MS, but also from other sources). I'm not sure what happens in VFP if
>someone sends you a project that uses an incompatable (generally newer or beta)
>control? In VB, the project loads sans the control. The design-time property
>settings are gone. Bummer. If they were coded, you'd just drop in your own
>version of the control, and be off to the races.

Oh, yes, I've seen this one before... good point. You don't mean to hand-code all form and control properties, though, do you?