DaleHohm

Many modern forms don't use the Submit action, but rather JavaScript tied to another element that may look look a Submit button - which is why the Click works. Another possibility is that the page may be looking for the "value" of the Submit button that is sent with the form data when a submit button is clicked, but not on a Form Submit action. Dale

The way it works is that the browser sends a "request" to the web server for something. The Server sends back a "response header" that tells the browser the type of content it is going to send back and how many bytes of data to expect (content-length), then sends it. The browser reads data until it gets the expected number of bytes... if the expected number of bytes are not received, the browser will not set its readyState to complete... _IELoadWait sets a timer and loops checking the readyState until it goes to complete or until the default 5 minutes pass (when the LoadWaitTimeout message is given). As SmOke_N said, you can look in IE.au3 at the _IELoadWait function to see how this is done. Dale

The SLEEP() suggestions will not help you in any way. The important message is 6 ($_IEStatus_LoadWaitTimeout) - Load Wait Timeout. This means that _IENavigate waited 5 minutes for one of the sites to finish loading and it didn't. Internally, it is waiting for the document ReadyState to change to 4 or "completed" - you may actually see HTML rendered in the browser, but it still thinks it is waiting for more information from the web server. You can circumvent this default behavior in _IENavigate (it is actually a behavior of _IELoadWait that _IENavigate and many other _IE functions call for you) by passing the NoWait flag to _IENavigate and then putting in your own logic to see if the browser page is ready to work with. _IELoadWait also has a configurable timeout value that you can set... see the helpfile. All that said, what jdelaney suggests is also prudent. Dale

If the documents are actually stored in SharePoint and are being accessed over http(s) by the Groove client app, you may be able to examine network traffic to see where it is actually pointing. You may be able to use netstat or Fiddler (Google them) to see. You may then be able to connect directly, unless the authentication model used throws you another curveball. Dale

See _IEPropertyGet and it's example. Use it to position the mouse pointer and then click with MouseClick Dale

The .Navigate method has no return value, so you must attach to the new IE on your own. I'd suggest that you put the _IEAttach into a loop, waiting for the new window to be found. Something like: While 1 $oIE2 = _IEAttach("http://www.autoitscript.com/forum/", "url") If IsObj($oIE2) Then ExitLoop WEND SmOke_N's method will work too. Dale

#include <IE.au3> Const $ie_new_in_tab=0x0800 $oIE = _IECreate("http://www.autoitscript.com") $oIE.Navigate("http://www.autoitscript.com/forum/", $ie_new_in_tab) $oIE2 = _IEAttach("http://www.autoitscript.com/forum/", "url") _IEQuit($oIE2)

Or $oChildren = _IETagnameGetCollection($oUL, "li") Dale

You can also use .fireEvent method to to trigger arbitrary events. Search the forum or see IE.au3 source to see how it is done. Dale

You may not be allowing enough time for the table to repopulate after clicking next before you try to read it again. Try putting in a Sleep(xxx) to see if it solves your problem. If it does, then use a more sophisticated delay (you may be able to use _IELoadWait on the table or you may have to check it's content more directly). Dlae

Try outputting $htmlResultString somewhere to see if it contains what you expect it to contain. Examine @error after your _IE calls to see what error status might be returned. Dale

Use embedded when you want to wrap a browser instance inside your own UI and controls. Otherwise, much simpler to simply use the full browser. Regarding orphaned processes... make sure that _IEQuit() is called before script exit - normal or abnormal. Dale

I don't see anything in all of what you have posted that shows the string "enGB" that you are trying to select. You need to isolate the control that presents it and figure out how to manipulate it. Dale

There is something unique in the content you are writing to the browser that is causing readyState not to make it to Complete (or 4). Does the browser contain the content that you expect it to contain after the _IEDocWriteHTML? If so, you can bypass the intrinsic _IELoadWait in _IEDocWriteHTML by using _IELoadWaitTimeout(0) before your call and _IELoadWaitTimeout(30000) afterwards to reset it to five minutes. Dale

The element you highlight here is not a form element, but rather a link (<a> tag). You'll need to use _IELink* functions or _IEAction, click to activate it. You will have to drill into the frames, layer by layer. Use _IEDocReadHtml and search the text returned to insure you found your link in the frame. You will also want to set up a COM error handler to see if you might get an Access is Denied error when traversing frames (caused by cross domain scripting). Dale