Jump to content
Sign in to follow this  
alsolh

Help in frames in ie.au3

Recommended Posts

alsolh

Hello there this autoit script is the best control software i have ever used..

however i have a small problem in fetching a frame and this is the html code:

<HTML>
<HEAD>
        <script src="js/util/Grid.js"></SCRIPT>
        <script src="js/util/Common.js"></SCRIPT>
        <script src="js/util/onsubmit.js"></SCRIPT>


<title>Account Inquiries</title>


<form name="mainPage1" >

<FRAMESET rows="45%,*%" cols="*" framespacing="0" frameborder="NO" border="1" id="inqiryFrameSetId">
    <frame src="../../../FixedAccInquiryAction.do?accountId=272399500&fromCMS=null&operation=3&searchPage=SOHACCOUNTIDINQ" name="accountFrame" noresize >    
    <frame src="../../../AccountServDtlInquiryAction.do?operation=3&DEBUG=TRUE&accountId=272399500&fromCMS=null" name="relLinksFrame" noresize> 
    
    
    
</FRAMESET>
<noframes>
</form>
<body>
</body>
</noframes>
</HTML>

as you see the frame "accountFrame" is inside a form and inside a frameset

i tried:

$oFrame = _IEFrameGetObjByName($IEObj,"accountFrame")

but it gets an error

and tried

$oFrame = _IEFrameGetCollection($IEObj,0)

but when i read the html content it is empty

can anybody help me?

Edited by alsolh

Share this post


Link to post
Share on other sites
DaleHohm

Perhaps there are more frames involved.

ConsoleWrite(_IEDocReadHTML($ObjIE) & @CR)

Should show you the source above, does it?

Dale


Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×