SZ_1
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Error "Object doesn't support this property or method" using .Exists of returned object from Find
At AlexKaras Thanks for your reply. I had realised that after I posted the messages and I already pointed this out on this thread on stackoverflow: https://stackoverflow.com/questions/55857445/sometimes-exists-property-is-not-supportedRe: Error "Object doesn't support this property or method" using .Exists of returned object from Find
TestComplete 11.31. I could upgrade it to 12.XX but decided to stay with 11.31 as in the past when I upgraded the main version of TestComplete, some of the test scripts would stop working and needed to update.Re: Error "Object doesn't support this property or method" using .Exists of returned object from Find
TanyaYatskovska Also as I mentioned in my original post, checking for not null or null does not throw any error but I need to know if checking for not null will guarantee no problem accessing the properties of the objects. I tried this on the niewPort and it worked so far as viewPort has been alwasy found.Re: Error "Object doesn't support this property or method" using .Exists of returned object from Find
Delay did not work. I already tried different times of delay even as long as 1000, 2000. I have found a workaround: If I access a different property e.g. Name before access Exists, there is no error at .Exists: The problem is that I need to add this .Name line everywhere before .Exists statements for all of the objects. Hope this helps you to find some clues what might be the cause.Re: Error "Object doesn't support this property or method" using .Exists of returned object from Find
Thank you all for your responses. I will answer all of your questions here: >>> What does the result of the variable "viewPort" return to you? ViewPort is a WinFormsObject with properties as it should have. The image below shows some of them including the property Exists with value True: As to response from tristaanogre As I mentioned in my post, this happened to many objects not just this one. In all cases where the error occurred, the objects were found with Exists propertt being either False or True. The only change I can think of is to have .Net framework 4.8 installed. The error started after that. >>> We you able to find the solution? No
