Hi,
Infopath is a lot more stable when editing ProcessGuidance.xml from Build 97, but I am still having the occasional problem. However, it seems to be related to specific Content Items.
For example, whenever I select the "Develop Threat Model" activity, Infopath crashes.
Is there a workaround other than editing the XML directly
Regards
Allen Jones

InfoPath crashing when editing specific Process Guidance Content Items (Build97)
PCry
Hi Allen,
Please be sure you are using Office Service Pack 1. There are improvements in SP1 that will help when using Infopath. You can check by going to the Help menu in Infopath and selecting About Microsoft InfoPath. Make sure the about dialog shows SP1. If you don't have it, you can download it from the Microsoft Office Web site.
Also, the ProcessGuidance.xml file, schema, and template seem to push InfoPath to the max. Although crashes do not happen often, here are some tips I've learned while authoring that seem to help.
- In general, avoid having more than one instance of InfoPath running.
- In general, avoid clicking or scrolling rapidly while InfoPath is processing data or rendering. For example, when you first open ProcessGuidance.xml there is about a 5 second lag while it reads the file. I wait until it is done before selecting a content item.
Hope this helps,
David Chesnut MSFT
(This posting is provided "AS IS" with no warranties, and confers no rights.)
mafred52
Hi David,
Trying to make a simple change to the ProcessGuidance.xml using MS InfoPath application to see how this works. I made changes to files to enable edit mode according to the "MSF Process Guidance Customation Guide". I then open ProcessGuidance.xml file using InfoPath. I then click on the "Project Manager" role item, scroll down to bottom of the page to the "Content" Section. In that section I changed the "Content Name" from "Project Manager" to "Product Manager" and tried to save the file then I got a dialog box indicating a following error
"This form contains validation errors that are not in the current view.Errors are marked with either a red asterisk(required fields) or a red, dashed border(invalid values).
If you cannot find an error in other view, there might be a problem with the form's design.
The form contains the following errors:" and contained many more error messages.
Please kindly provide a solution in order to solve this problem.
Thanks