[trobbins@echn.org]

FYI – I am working with Ted…

[trobbins@echn.org]

I really need help on this.  This impacts a script that runs at 4am every night and it requires a person to connect and rerun it every night at that time.  This problem impacts about six of our scripts….
 

[trobbins@echn.org]

Have you tried the command using an explicit window handle?

I have Windows dialogs that popup when running the bws script from a powershell call and this is a problem when using regular BWS 'rules' and 'actions'.  SmartDialog has an optional 'handle' parameter and I am giving it the Windows dialog handle to set  the file name and push the button.

[trobbins@echn.org]

I took a look at the window objects (for the Open window) and here is what I see.  <item number><Handle> <windows name>
1 6357788 : 
 2 8062306 : 
 3 6881998 : 
 4 3212930 : Internet Explorer
 5 3343924 : 
 6 2951438 : 
 7 3081696 : 
 8 2492690 : 
 9 2754668 : Internet Explorer
 10 6882162 : 
 11 3606804 : 
 12 5637090 : 
 13 6620090 : 
 14 3278970 : 
 15 3999950 : 
 16 2033758 : 
 17 7079180 : 
 18 13764670 : 
 19 1968228 : 
 20 5767794 : 
 21 2885840 : Open
 22 4719718 : 
 23 8192720 : 
 24 1902878 : 
 25 5244332 : Namespace Tree Control
 26 6226596 : Namespace Tree Control
 27 7864550 : Tree View
 28 5440020 : 
 29 7734198 : Shell Preview Extension Host
 30 4392372 : 
 31 2950830 : ShellView
 32 5112886 : 
 33 4065408 : 
 34 3279338 : 
 35 5440050 : 
 36 8193092 : 
 37 6882484 : File &name:
 38 5834380 : 
 39 8454748 : 
 40 2034182 : 
 41 5702532 : Files of &type:
 42 4458050 : 
 43 15468482 : &Open
 44 6882310 : Cancel
 45 4720798 : 
 46 7012468 : 
 47 9765480 : 
 48 5440140 : 
 49 6293260 : 
 50 5310374 : 
 51 6292276 : &Help
 52 3933598 : 
 53 3999960 : 
 54 2950534 : 
 55 5440458 : Navigation buttons
 56 4982042 : 
 57 7340556 : Up band toolbar
 58 1706380 : 
 59 2951070 : 
 60 3015968 : 
 61 6619948 : Address: \<destination folder>
 62 2623292 : Address band toolbar
 63 3016214 : 
 64 6161212 : 
 65 6358002 : 
 66 7210186 : 
 67 5440262 : 
 68 10748856 : 
 69 10158738 : 
 70 2295434 : 
 71 3016768 : 
 72 6423708 : BAR.ROG (F/LIVE.MIS/30) 
 73 5310224 : 
 74 3671870 : 
 75 7078424 : 
 76 4392996 : MSCTFIME UI
 77 8521274 : Default IME

There are two "Open" handles that are showing up in the Windows Inprocess (Direct.M.W.hWnd).  One is "Open" and the other is "&Open".  There is only one Cancel. 

Using SmartDialog I am trying to push the "Open" button after filling in the filename.  
My wHandle is coming from FindWindow(0&, "Open")

SmartDialog(wName,"Open<PushButton>",wHandlel).Click. The focused default keywords at the end of <PushButton> did not work.

I tried using "&Open" in SmartDialog and that does not work either.  

Is this a focus issue?  Is it a Windows handle issue?

 

[trobbins@echn.org]

Thank you.  It still does not work. It runs but there is no action.  I wonder if it is focusing on another "Open" statement in the dialog.  Cancel works every time.

[trobbins@echn.org]

Hi, thank you for the reply and suggestion.
I have setup a shortcut that runs RDPExit to ensure that the remote user exits the system properly – but, unfortuantely it did not work.  

The problem that I am having is that I cannot detect when a windows dialog that is not attached to the Meditech window comes up so there is no way to handle it.  The only action I can take is to time out the step.  This is a problem when I have a Meditech operation changes duration based on amount of data.  If I knew that it always took 15 seconds, then I could handle it with a timeout, but if it ranges from 15 seconds to 4 minutes, it is a bit more difficult.  If I attempt to restart, there is no guarrantee that the same problem will not happen again.  

Is there a way to detect a window popup and handle it in VBA? 
Is there a way to enable desktop interactivity in powershell when I call the BSS script?

Thank you!

[Author]

Posts