Re: InfoPath issues fixed in SP2

Patrick Halstead — Wed, 09 Nov 2005 09:10:47 GMT

Anders - great post! Thanks for the info.

I think the best fix in SP2 is the dreaded DOM Event Handler issue where DOM Event Handlers were stripped out of solutions with managed code in certain instances depending on interaction between Visual Studio and InfoPath Designer.

The other important issues we have found in the last year have been IE bugs (issues in Trident) which caused InfoPath to crash. Thankfully, the recent hotfixes have reduced the occurrence.

Patrick Halstead [InfoPath MVP]
InfoPathDev

InfoPath issues fixed in SP2

AndersR — Wed, 09 Nov 2005 08:46:35 GMT

For those interested, here is a list of whats fixed in SP2.

http://support.microsoft.com/kb/906426/

Issues that were previously documented in the Microsoft Knowledge Base
Office 2003 SP2 fixes the InfoPath 2003 issues that are described in the following hotfix packages:

http://support.microsoft.com/kb/886706/
Description of the InfoPath 2003 post-Service Pack 1 hotfix package: September 30, 2004
http://support.microsoft.com/kb/890952/ Description of the InfoPath 2003 post-Service Pack 1 hotfix package: December 17, 2004
http://support.microsoft.com/kb/895405/ Description of the Microsoft Office InfoPath 2003 post-Service Pack 1 hotfix package: March 11, 2005

Issues that were not previously documented in the Microsoft Knowledge Base
Office 2003 SP2 fixes the following InfoPath 2003 issues that were not previously documented in the Microsoft Knowledge Base.

You receive the "InfoPath cannot create a new, blank form" error message when you try to open a redesigned form

If you change a designed (extracted) form in InfoPath 2003, all the conditional formatting is removed from the form.

When you try to open the redesigned form, the form does not open. Additionally, you receive the following error message:
InfoPath cannot create a new, blank form.
InfoPath cannot open the form. To fix this problem, contact the system administrator.
If you click Show Details, the following information appears:
Form template: file:path\manifest.xsf
InfoPath cannot open the following view: View 1
The following view file is not valid: view1.xsl
The .xsl file is not valid XSL.
Expression expected.

You receive the "InfoPath cannot open the following form" error message when you try to open a solution in design mode

You try to open a solution in design mode. This solution contains a group that is bound to a repeating group. In this situation, the solution does not open. Additionally, you receive the following error message:
InfoPath cannot open the following form: path\filename.xsn
Microsoft Office InfoPath cannot open the selected form.

Some database values are overwritten when you use a form to query a database

When you use a form to query a database, some database values may be overwritten in the query results.

InfoPath 2003 unexpectedly quits when you design a form that is connected to a Web service

When you try to design a new form that is connected to a Web service, the form is not created. Additionally, InfoPath 2003 unexpectedly quits without an error message.

You receive the "The form template is invalid" error message when you try to open a solution that contains a nested "List Box" control

You try to open a solution that contains a nested List Box control. If the nested List Box control is bound to a repeating field, the solution does not open. Additionally, you receive the following error message:
The form template is invalid.
If you click Show Details, the following information appears:
InfoPath cannot open the following view: View 1
The following view file is not valid: view1.xsl
The .xsl file is not valid XSL.
Expected token ')' found '['.

HTML information is not saved when you use the Export to Web feature

When you use the Export to Web feature to save the form as a Single File Web Page (MHTML), HTML information is missing in the file. Only the MHT header information is saved in the file.

Ink entry mode unexpectedly increases the CPU usage

When you use a form in ink entry mode, the CPU usage unexpectedly increases.

You receive the "InfoPath cannot run the specified query" error message when you run a query in a form

When you run a query in a form by using ActiveX Data Objects (ADO), the query does not run. Additionally, you receive the following error message:
InfoPath cannot run the specified query.
If you click Show Details, the following information appears:
The XML data returned from the data source does not match the XML Schema for this form. This discrepancy might be caused by the data source returning multiple rows when InfoPath expects only one. Attribute 'PID' is not allowed on element 'http://schemas.microsoft.com/office/infopath/2003/ado/dataFields}Ones', according to Schema.

General

Re: InfoPath issues fixed in SP2

InfoPath issues fixed in SP2