Quote Originally Posted by Hosam AL Dein View Post
I could reproduce the scenario which causes this problem and it is such a strange and tricky .

https://www.youtube.com/watch?v=IaxZ...ature=youtu.be

I was limited to 15 minutes of recording so , there is an uncompleted test result at the end of the video but it should be enough to make the point clear for now .

Summary for video :

The scenario :

1- Add a new user control
2- Place normal textbox or any VB6 intrinsic controls in the user control .
3- Place any VBCCR control in the user control
4- In the UserControl_Initialize event , add these lines of code .

Lets say you used a VB intrinsic Textbox and a VBCCR CommandButtonW . Add these lines

Code:
text1.text="Hello"
commandbuttonw1.caption ="Hello"
5- The problem happens
6 - Uncomment the code , The problem now disappears .
7 - Put the following code in the same event
Code:
Dim s as string
s= "Hello , I prove that not all code causes the problem , It is only for the code that draws an item in the user control"
8 - With this previous case , the problem does not happen .

More details and tests are found in the video for tests on the ComCtlsDemo project

Thanks everybody for your help and sorry for bad English .
It's a very bad idea to make some code involving the child usercontrol in the host usercontrol inside the UserControl_Initialize() event. The UC Ambient.UserMode property is not meaningful at that place. Please set your code that involves the child usercontrols in the UserControl_ReadProperties()/UserControl_InitProperties().