>Larry,
>
>I spoke with them and managed to get an example working. It must be something particular to ChartFX.
>
>As an aside, I found that dropping a ChartFx control on a form was much more problematic (flashing while instantiating) as opposed to doing a form.createobject on the form.init. This was particularly true since my form.init moves the window to the its last memorized position.
>
>Thanks again,
>

Tom,
Sometimes this isn't possible on the customer's PCs because you need a design-time license for it. See MSKB#192693 for more details.

I don't know if this is available on the ChartFX control but if you can get the windows handle (hWnd) for it, you can use the LockWindowUpdate API function (see API#12721) to lock the control so it won't show the movement. After the form movement is complete, unlock it and it will look like it simply went from one place to another.

HTH.