Object/TypeName/TypeOf weirdness! (bug?)

[Pallex]

Hi!

ok, i have a situation where, in my immediate window i can go:

?typename(fred)

and i get

"TextBox".

I go:

If TypeOf fred is TextBox then ?"textbox" else ? "not textbox"

and i get


"not textbox".

I`ve tried different types for fred. Ideally it would be object, as i want to iterate through each of the controls on a form, so i`d get errors/have to write error handling code if i used type `textbox`.

Any ideas whats going on? Bug in VB (6, no service pack)? Misunderstanding of TypeOf/TypeName?

This code is in a DLL, if thats relevant.

[Nucleus]

The typeof is statement only works if the object library is currently selected in the references dialog box.

On the other hand typename doesn't require the object class to be present in the current application or in the references dialog box. So use typename() not typeof().

[crispin]

could you use something like this?

Private Sub Command1_Click()
Dim ctrl As Control
For Each ctrl In Me.Controls
If TypeOf ctrl Is TextBox Then
    MsgBox ctrl.Name
End If
Next ctrl
End Sub

[Pallex]

The called dll does this:

if typeof fred is textbox then
ok,do more processing on textbox
else
not a textbox, so fail
endif

My code passes it a textbox, and it fails.

Its as if the `typeof` command takes the two objects (fred, and a textbox), and checks them, but not using their name (which presumably is `textbox` somewhere inside the object) but checks some other property (like an internal version number or something).

Bizarre.

[Nucleus]

Doesn't typename work either?

It is documented that typeof is, will not work in as many circumstances as typename.

[Pallex]

"Doesn't typename work either?

It is documented that typeof is, will not work in as many circumstances as typename."

well, typename returns `textbox`, which is fine.
and yes, typeof only works as part of an if..else statement.

The prob is that i dont have the sourcecode to the part of the code which uses typeof.
I have an earlier version of the DLL`s sourcecode, for documentation purposes, but i cant change the corresponding code in the current version of the DLL, as i dont have the current version (and won`t ever have).

If that makes sense!

so i can see why its failing, i was just interested to know why!

(The dll provides some support for keyboard input into a textbox and displaying the output (formatted). seeing as i cant convince it that my textbox is actually a textbox, i`ll have to do the handling myself. Tedious.)