I haven't run into this before, so my first suggestion would be to call compuware tech support and see if they can help. My guess is that the "sub-class" is what is causing the problem, and without having a sample of the app, I am afraid that I can't be of much help.
If you identify the object, what is exactly the class name? Or are you not able to get the focus on the text box (does it only recognize the parent object!!)?
I had a similar problem with one of my applications. I was able to hang me thru the tree browser of the identify-tool and found finally the text box object. It was not accessable thru the cursor (the round mouse thing you use to search on the screen), but in the tree, it was there. the class name was something like "RCEditbox", so I created a Alias Map Entry for it. Afterward, I created a Object Map Entry for the Edit Box (therefor you need to browse thru the object tree of the identify window). Inside the script, I had to use the following code type text into the text box:
Dim MyTextBox as TEditBox
Set MyTextbox = EditBox("Name_of_your_TextBox_Object")
MyTextbox.SetText ("Your text to write in the Edit Box")
Hope this helps
[ 04-27-2004, 07:00 AM: Message edited by: Adrian Z ]
That's a good point... the object may be "shielded" by another object. Just a note, if TP sees it as a true object, in this case an EditBox..., it is not required to dim the object. You just have to get the attach name from the Tree.
EditBox("Name_of_your_TextBox_Object").SetText "Your text to write in the Edit Box"
In my case, the TreeView runs into miles of lenght and I am investing most of my time not in scripting but in searching for that attach name in that HUGE tree. Are there any tips/suggestions that can help me in saving time. Help me ;-( this will save lot of time for me.