I am attempting to utilize OCX's in VFP 6.0 sp 3. Namely DBI-Techs control pack (54 different controls). I am using the controls by the following methods.

1). Load all controls in a single VCX.
2). Created a second VCX that contains one container for each control.
This container loads the OCX into itself at runtime. This allows for seperation of the control license file ETC from my source code.

3). I have created a property in the container that corresponds to each property for a control. Using the Assign method for the property of the container I control the property of the OCX.

4). I drop the container on my forms. My forms talk to the the container the container talks to the OCX.

5). I only load forms as a class not via DO Form.

I am having different control drawing problems, Sizing (Height, Width, Top Bottom) at init. On some controls I am having problems at run time with refreshes, but most of my effort so far has only dealt with getting the forms to draw properly at runtime.

DBI says that VFP has problems with drawing OCX controls that other enviroments do not have. I am having different problems with different DBI controls so I suspect that all problems are not VFP's. One control in particular sizes differently based upon the position it is placed upon the form.

When I look at the VFP demos where OCX's are dropped directly on forms I do not see the same problems that I am getting by loading via containers.

I am looking for a list of gotchas and work arounds others have experienced with other OCX's when it comes to drawing the screen when loading OCX's in a manner similar to this.