Yes. But I posted it here also since the main app is VB6 even though the DLL is VC++ 6.

Yes. The DLL is not a problem since it is compiled with _UNICODE, UNICODE with no problem. The problem is VB6 translates all DLL calls to ANSI even though it is UNICODE.

Currently I am working on an old VB6 app to be compatible with UNICODE.

This app has SSTab and within this tab, there are user control q1, q2, q3 and so on. For q1, it has the following code:

Private WithEvents q1 As VBControlExtender
Private progID As String

procId = “ALCTX10.CTX10.1”
Set q1 = Controls.Add(procId, “q1”)
myTab.tab = 1
q1.Move borderSize, topMargin, myTab.Width - borderSize * 2, _
myTab.Height - borderSize - topMargin
q1.Visible = True

The procId is referring to VC++ 6 DLL. All user controls are using this DLL.
For VC++ 6 DLL, I added ",_UNICODE, UNICODE" into the preprocessor definitions under the project setting of VC++ 6.
And compiled the DLL again and then brought it back to VB6.

The problem is I am still getting the same UNICODE issue from VB6 app.
I am using a foreign version of Windows XP so it is not the font problem.
I can’t just replace this DLL with UNICODE supported TextBox or RichTextBox since there are too many things going underneath the DLL.

I would appreciate very much if anyone sheds a light on this problem. Thanks.

Currently I am working on an old VB6 app to be compatible with UNICODE.

This app has SSTab and within this tab, there are user control q1, q2, q3 and so on. For q1, it has the following code:

Private WithEvents q1 As VBControlExtender
Private progID As String

procId = “ALCTX10.CTX10.1”
Set q1 = Controls.Add(procId, “q1”)
myTab.tab = 1
q1.Move borderSize, topMargin, myTab.Width - borderSize * 2, _
myTab.Height - borderSize - topMargin
q1.Visible = True

The procId is referring to VC++ 6 DLL. All user controls are using this DLL.
For VC++ 6 DLL, I added ",_UNICODE, UNICODE" into the preprocessor definitions under the project setting of VC++ 6.
And compiled the DLL again and then brought it back to VB6.

The problem is I am still getting the same UNICODE issue from VB6 app.
I am using a foreign version of Windows XP so it is not the font problem.
I can’t just replace this DLL with UNICODE supported TextBox or RichTextBox since there are too many things going underneath the DLL.

I would appreciate very much if anyone sheds a light on this problem. Thanks.