I have not seen much about this. But I finally just dropped the control on a form, saved the form then opend the SCX table to see what the hell was different. For that control, I see there is some compiled code in the Ole memo field that is unintelligible that I am assuming is what satisfies the "licensed for use" criteria that we can not put in a PRG file. The Ole2 memo field contains the class name of the control. So it's SCX, here I come. < sigh >

>I agree it's easer to maintain PRG objects - and they are less-likly to corrupt!
>
>But, that being said - I checked a PRG (main) form project. It uses sliders from Lib.2
>frmR6.addobject('SideSlider','subSideSlider','MSComctlLib.Slider.2')
>The form is opened with:
>frmR6.Show
>read events
>
>It's VFP 7/Install Shield Setup. One difference may be that the "about" screen, report server and table manager (little forms) are SCX. But the Main (working) form is all PRG.
>
>It branches Main.PRG - Main.PRG.Form - the about and others (SCX) are "children" of Main.PRG.Form (all are modeless).
>
>Maybe the fact that the Main form spawns SCX's is why this project works. A suggested workaround might be to have your PRG form spawn a "do-nothing" invisible SCX form to see if that has an affect.
>
>It should work - have you seen anything that indicates a PRG form cannot instanciate Lib.2 outside the IDE?