No. Thats a bog standard Windows Dialog window.
I have a Delphi application. Some errors and popouts use Delphi generated windows. Some of them use the standard Windows Dialog. Depends how your devs have built it. You just need to handle them.
See: https://msdn.microsoft.com/en-gb/library/windows/desktop/ms633574(v=vs.85).aspx#system
If the caption varies, and you have mapped it using the caption as an identification property (sounds like you have), then the window won't be found next time it appears.
Thank you Colin for your reply. I didn't use caption to map it, I use xxx is just to replace the real caption but didn't mean it is varies. :)
TestComplete can't handle it no matter with mapped name or full name. We have this #32770 dialog window in other module with C# and can handle it well, except this one. :(
What is it mapped with?
As I say, my current project is a C# Application, which launches Delphi modules, which all write to SQL DB's. I have to interact with all 3 parts. The Delphi modules do throw those type of Windows Dialog boxes (as well as Delphi native ones) and my tests handle both just fine.
I have them added via MSAA.
I don't have any problem with them.
Although, you say it hangs? Even if left all night, it hasn't timed out? That doesn't sound right. I would have expected it to time out and fail if it was a simple "not found" problem ....
Your window is modal. aka - it blocks all other objects within the application until it is cleared.
I suspect whatever you mapped it with is not being recognised at runtime. Add it to MSAA and map it reliably and all should be well. Mine is ....
