>Any recommendations for migrating VFP scx forms containing "older" versions of ActiveX controls (and related code) to a new development machine that will have "newer" versions of the activex controls? (the older versions of the activex controls will not be present on the new machine)

Hi Chris:

You may change it in plain text if you convert your form with FoxBin2Prg.
The generated text can show you something like this:

	ADD OBJECT 'oleRTF' AS olecontrol WITH ;
		Height = 197, ;
		Left = 28, ;
		Name = "oleRTF", ;
		Top = 20, ;
		Width = 297
		*< END OBJECT: BaseClass="olecontrol"  Nombre="frm_olertf.oleRTF" Parent="frm_olertf" ObjName="oleRTF" OLEObject="c:\WINDOWS\system32\richtx32.ocx" Value="0M8R4KGxGuEAAAAAAAAAAAAAAAAA........" />

So you can change the "Nombre" property value with your new name.
The "Value" property have the settings you have configured on your OCX, and you can test if keeping this "Value" your new OCX keep working (is compatible) or not.

Finally, once changed the OCX name, you can regenerate your form from the text.

Regards.-