| || |
Silk 5.5 declares VB6 app as custom window
Could anyone help me to understand this:
My company got an eval version of Silk I wrote a bunch of scripts testing VB6 app, then we purchased the tool and got Silk 5.5, when I tried to use my scripts with 5.5 they are all broken since new 5.5 sees all as CustomWin, whereas old inc identifies VB controls - BCommandButton, VBTextBox etc.
PS.I did enable ActiveX extension for Silk and for agent on the same win2000 machine.
Re: Silk 5.5 declares VB6 app as custom window
You posted your inquiry a few weeks ago - did you resolve this yet? Sounds like a configuration issue to me. SilkTest should not have the problems you described on a VB app.