ContributionsMost RecentMost LikesSolutionsRe: How to handle non standard windows with regards to object mapping Alex, This was what I was worried about, and trying to avoid. I had for the most part assumed I might have to settle for one of those options. I am currently at a point where I am trying to future proof the scripts as I know these items could eventually change location which would totally throw off my scripts. Now a screen/image scrape might be more feasible to search for that option as it could simply move. Any suggestions for implementing and checking this concept? I would like to avoid this, but it seems my chances are slim and they way their implemented a lot of their objects doesn't seem the interpreter will pick them up. Re: How to handle non standard windows with regards to object mapping I unfortunately do not have access to the dev team as this is an external third party product. I am checking into the implementing MSAA manually as I have selected the automatic settings to no avail. Thanks Re: How to handle non standard windows with regards to object mapping Sorry for my delay! From what I can tell the application is most likely written in C++. The top level object is labeled wndgsi_window. When utilizing the Object Spy etc, this is mapped as the main application window. So say I am clicking on the menu option "Tools". The mapping is placed as a click operation in wndgsi_window (50,50). So it is now mapped as click on the main screen at point 50,50. It doesn't give any deeper object label then that. Is there anything you might suggest as far as TestComplete settings I can try? I know I can't build or recompile the tool. Re: How to handle non standard windows with regards to object mapping Mrunal, Thanks for the response. Unfortunately, this seems similar to several of the steps I've tried before. For some reason, when I try to map certain objects, it can only identify the window that is is contained within. I am not sure if my issues makes any sense. So when I tried to highlight or select the specific item using Select Object options via Menu Action, all it seems to identify is the window contains the item I am interested in mapping. Maybe I am not doing it correctly... How to handle non standard windows with regards to object mapping I am having trouble mapping objects in a Desktop application that doesn't utilize standard windows format. So essentially when trying to map say a menu item, it gives me screen coordinates instead of the actual object name of say |File. Solved