Sylvrwynd

Actually, I have plenty of GuiSwitch() calls... but I solved it on my own.. I awoke to an epiphany... When I choose to update the customer info on the new GUI, I delete all controls on the main before I minimize and switch to the Customer Update GUI. Then when I close the Customer Update GUI, I call the dyanmic Button function which re-builds the controls on the Main GUI based on the new customer info.

<CODE REMOVED> I have merged the important files into the main code and commented out the includes. All other functions work fine. Thanks for your help.

Do you think putting it all in one file and removing includes would change how the calls work?

I also forgot to mention, you could test the TEXT of the window title until it reflects what you are looking for... EX Opt("WinTitleMatchMode",2 ) WinWaitActive ( "AutoIt Forums" , "Replying in How to detect new windows are openned..") For your case, the latter solution would probably be a better choice since IE changes the text of the title based on the webpage. The Former case was where the window title doesn't change but the contents do... Sorry for the confusion.

Have you tried using SEND() and Copy a portion of the open window into clipboard, then use ClipGet() and test it for what you are looking for? EX. Func TEST() Local $TEST1 WinActivate("Internet Explorer") WinWaitActive("Internet Explorer") DO Send("{HOME}{TAB}+{RIGHT}+{RIGHT}+{RIGHT}!EC") $TEST1 = ClipGet() Until $TEST1 = "WEL" ; Suppose first three letters of text on screen is WEL (WELCOME) EndFunc Something like this would run until $TEST1 = what you were waiting for. Obviously the keystrokes would have to be tested manually by you first, but then once you code those proplery, it will run well. I hope this helps!

Good morning/afternoon/evening/night Everyone! I am working on a program that does a series of things: We use AS400 Emulators at my work, and this program will interface with multiple windows to accomplish tasks. I have already succeeded in creating a "PerUser" login info save in the registry and a customer database that varies per user. However, on my main GUI which I call the "Widget_Window()" I want it to build buttons based on only the customers that exist in the database, and not blank entries. I have succeeded in accomplishing this, however, When I close the GUI to the Customer Data Entry, and I switch back to the Main Widget_Window, I run into a series of errors depending on how I try to takle this obsticle. A) I have tried GuiDelete($mainwin) then CALL("Widget_Window") This tends to lock up the entire process, not even closing the Customer Data window. I then have to Ctrl+Break to get out of this problem, with no errors generated. I have tried Putting a refresh function call in the While loop of the main GUI, but that flickers all of the buttons... (not what I want.) C) I have tried to write a refresh function that I can execute when I exit the Customer Data GUI, but it locks everything up as well. I wrote something like this: This is called from a loop that is SetOnEvent, MustDeclareVars.... Assume all Variables are pre-defined (They are - not getting errors of that nature) Func REFRESHMAIN() $TEMPGUIREFRESH = GuiCreate("TEMP",10,10) GuiSetState(@SW_SHOW) ; At this point, AutoIt deaults focus to this new GUI GuiDelete($mainwin) Call("Widget_Window") GuiSwitch($mainwin) GuiDelete($TEMPGUIREFRESH) EndFunc Now, according to my thought processes, I create a gui, switch to it, delete the old gui, call the old gui back which refreshes it, then switch to it, and delete the temporary GUI. At this point, everything looks great until I try to click anything, or even try to exit. IT DOES NOTHING. The button creation works great, but then thats all she wrote. Gui refreshed but stuck on stupid. Any ideas??