_IE set value of checkbox on win x64

[Jannick]

Hello,

I've been trying to set a checkbox on html page but i always get a warning: _IEFormElementCheckboxSelect, $_IEStatus_NoMatch

When i tried this script on a different computer (32bit) it worked like a charm.

I was wondering if this is a bug or is my implementation is wrong.

I would like to run this script on x64 and x86 so i there a way to implement this code that will work on both os'ses

#include <IE.au3>
$oIE = _IECreate("http://www.somepagewithcheckbox")
$oForm = _IEFormGetCollection ($oIE, 1)
_IEFormElementCheckboxSelect ($oForm,0,"",1,"byIndex")

I tried the "byValue"-thing but i gives the same error (warning)

HTML code of checkbox:

<input name="agree" type="checkbox" id="agree" value="true" onchange="ckRegForm()" />

Jannick

[DaleHohm]

I see no reason that this should work differently on x64, the function does nothing exotic.

Based on the HTML you supplied, I would try this call:

_IEFormElementCheckboxSelect ($oForm,"true","agree",1,"byValue")

Dale

[Jannick]

Hi DaleHohm, tnx for replying

I suspect it can have something to do with the installation of autoit on my 64bit machine or that it is in fact a bug.

I took some screenshots, 1 on my 64-bit and 1 on my 32 bit machine.

As you can see, my 64-bit machine gives _IEFormElementCheckboxSelect, $_IEStatus_NoMatch

I would like to give you more info on my machine but i don't know what kind of info you might be interesting in.

Another differnce between my 2 computers is that my 64-bit machine uses ie6 and my 32-bit machine uses ie7 (could this have something to do with my problem)

Can you tell me if the uninstall of autoit 3.2.2.0 will in fact uninstall and erease all setting on my computer or should i manually delete some setting.

Tnx in advance

Script + screenshots

[DaleHohm]

OK, my best guess is that in fact the HTML source for that page is invalid (breaks some rules...). Different browser versions do a better job of recovering from such things thatn others.

I suggest that you run the page source through the W3C HTML Validator service (http://validator.w3c.org -- or see my sig). Repair the source if you have access to it. If you do not, there are almost always ways to work around it once we know whta the trouble is.

Dale