Hi all,

we have been looking out for a solution for the problem mentioned below.... PLEASE HELP

We have a problem with us here. We have created a dll which will externalize the font for an internationalization project. Based on the LocaleID it will change the language for the form.. This works perfectly in the form once the DLL is registered and referenced.

We would like to implement the same in a Usercontrol which we have by the dozen in each VBP. We are trying to do this in the UserControl_Initialize which gives an error

The code in the externalization in the class module is as follows:
ChangeFont.dll > Class Module
Public Sub SetFont(ByRef objClient As Object)
  If TypeOf objClient Is Form Then
    Call mdlChangeFont.SetFormFonts(objClient) 'For Forms
  Else
    Call mdlChangeFont.SetControlFonts(objClient) 'For UserControl
  End If
End Sub

For the Form we implement it in the Form_Load() as:
Private Sub Form_Load()
   Dim ext As New ChangeFont.clsChangeFont
   ext.SetFont Me
End Sub

Please let me know in which event of the UserControl should this be put whether UserControl_Initialize or UserControl_InitProperties or UserControl_ReadProperties or should we go ahead with the tedious process of changing the Font and the script in the UserControl to MS UI Gothic and Japanese.

This is an urgent requirement... HELP.............................

Regards
Arvind Krishnan

Hi,
i came across your problem quite late. I guess its already solved? Here is a link i found concerning that problem:
(PRB: TypeOf Operator Does Not Recognize Form Object)
http://support.microsoft.com/kb/194570/en-us
I have a similar problem at the moment. I would be very thankful if you could tell me how you solved the problem.

regards

as msdn states, Form and UserControl are objects that are recognized only inside the current project. Outside of it, they do not have any meaning. Just to explain this a little further, the dll can be written in C, where the concept of a Form does not exist. But even in VB, the "form" is just a pointer to a local object, that cannot be passed around project boundaries.
In this particolar case (internationalization) I put the code in a standard bas module (instead of a dll) that is included in all our projects, with a SetFont method used like:

Private Sub Form_Load()
   SetFont Me
End Sub

BTW SetFont is called also when the current locale is changed, so that our apps can update on the fly.

Marco