Forum Discussion
thomas_emich
12 years agoNew Contributor
I am having a very similar problem to this as well. Let me explain my story...
I started off with TC 7.5. Wrote quite a bunch of scripts. Things worked well. I then upgraded to TC 9.20.2460.7. The test machine I'm on is a Win 7 32bit SP1. I then ran the test script I have and then it came across the same sort of problem that this Post mentions. It complains about it can't find certain properties anymore. I did some further investigation and found some very odd behavior.
Before executing the test in TC9, it can properly identify the objects properties. Life is good. However, once i execute the test script, it then recognizes the object differently, causing the script to not work. Annoying...
I start TC9 and I load up my program I'm going to test. I use the Object Spy and highlight a form it is tripping up on. Before running the test, things are OK. I go to the Object Browser to get a better picture of things. I highlight the item 'VBObject("frmReportSelect"), and it properly displays the attributes and properties that are available to me. There is the set of Standard, Extended and Visual Basic properties. Looks like everything is working properly at this point... (See attached image)
I then execute a test script. I put in a breakpoint in the script to demostrate the problem, at the point where it brings up the 'frmReportSelect' form. Then I use the Object Spy again on this form, and then take it back to the Object Browser to see the whole thing again. But now things have changed. Where the item used to be called 'VBObject("frmReportSelect"), it is now called 'Window("ThunderRT6FormDC", "Report Expert", 1). And the looking at the attributies and properties of this item, it has lost the whole Visual Basic category. None of those properties are available to me any longer. This causes the script to no longer work (See attached image)
what is going on here.
I started off with TC 7.5. Wrote quite a bunch of scripts. Things worked well. I then upgraded to TC 9.20.2460.7. The test machine I'm on is a Win 7 32bit SP1. I then ran the test script I have and then it came across the same sort of problem that this Post mentions. It complains about it can't find certain properties anymore. I did some further investigation and found some very odd behavior.
Before executing the test in TC9, it can properly identify the objects properties. Life is good. However, once i execute the test script, it then recognizes the object differently, causing the script to not work. Annoying...
I start TC9 and I load up my program I'm going to test. I use the Object Spy and highlight a form it is tripping up on. Before running the test, things are OK. I go to the Object Browser to get a better picture of things. I highlight the item 'VBObject("frmReportSelect"), and it properly displays the attributes and properties that are available to me. There is the set of Standard, Extended and Visual Basic properties. Looks like everything is working properly at this point... (See attached image)
I then execute a test script. I put in a breakpoint in the script to demostrate the problem, at the point where it brings up the 'frmReportSelect' form. Then I use the Object Spy again on this form, and then take it back to the Object Browser to see the whole thing again. But now things have changed. Where the item used to be called 'VBObject("frmReportSelect"), it is now called 'Window("ThunderRT6FormDC", "Report Expert", 1). And the looking at the attributies and properties of this item, it has lost the whole Visual Basic category. None of those properties are available to me any longer. This causes the script to no longer work (See attached image)
what is going on here.
Related Content
- 7 years ago
- 4 years ago
Recent Discussions
- 2 days ago
- 2 days ago
- 5 days ago