>>>

>>>vBackSpace = 0x21
>>>

>>>
>>>or even:
>>>

>>>#define vBackSpace  0x21
>>>

>>
>>Wouldn't that be 0h21? 0x being for numbers, and 0h for strings. I know you and I and probably all of the Russians there would have this problem of swapping these accidentally...
>
>
>
>Nope. That is 21 HEX and it is 0x21 :-)
>if you look at the VB declaration they are defined as INTEGER not CHAR :-)

Then in VB having

vBackSpace = chr(21)

should raise an error, shouldn't it?