W3C home > Mailing lists > Public > www-forms@w3.org > April 2003

Re: [Re: [IBM Alphaworks - scripting errors with the browser component]]

From: <AndrewWatt2001@aol.com>
Date: Sat, 19 Apr 2003 03:59:32 EDT
Message-ID: <106.2251b1f7.2bd25be4@aol.com>
To: tvraman@almaden.ibm.com, jponzo@us.ibm.com, www-forms@w3.org, xforms@yahoogroups.com
In a message dated 11/04/2003 20:02:04 GMT Daylight Time, 
AndrewWatt2001@aol.com writes:

> Hi again,
> Thanks but I had already checked that.
> I have msxml4.dll, msxml4a.dll and msxml4r.dll in C:\WINNT\System32 - it's 
> a Win2k machine. All of the files show version as MSXML 4.0 SP1.
> Is there any easy way to check if IE 5.5 is "seeing" the correct version of 
> MSXML4? Unfortunately the versioning tips on netcrucible.com don't extend 
> to service packs of MSXML4.
> Andrew Watt

I was hoping for a follow up response from IBM but have solved the problem 

By upgrading from IE5.5 with MSXML4 Sp1 to IE6 the problem goes away. I can 
run all the AlphaWorks examples without the previously evident scripting 

I didn't test between my previous installation of IE5.5 and after applying 
all the security etc updates and the update to IE6, so perhaps there is one 
update to IE5.5 that is critical to the AlphaWorks browser component running 

Certainly, in my experience, IE5.5 (which had some but not all MS updates 
applied) with MSXML4 Sp1 doesn't work with the AlphaWorks XForms samples.

IBM might want to consider specifying IE6 as necessary for the AlphaWorks 
package, since it is evident that it doesn't work on all IE 5.5 installs.

Having said all that it is very nice to have an XForms implementation (I 
haven't tested how much is implemented yet) that will run in a conventional 

Andrew Watt
Received on Saturday, 19 April 2003 04:00:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:08 UTC