S
shenhong
I've created a form with more than 10 pages and faced the performance issue.
loading a form needs more than 20 seconds.
I'm using InfoPath 2003 + SP2, and I search from Google and found some
materials, but cannot change much, it still shows very slow.
What I've done are
1, Remove the <xsf:domEventHandlers/>, <xsf:ruleSets/> and use one gobal
OnAfterChange event handler to handler all events.
2, Limit the size of data passed via Web Service.
3, I also want to use C# code to take the place of <xsf:customValidation/>,
but cannot implement it. I've tried OnValidate, but this event fired only
after OnBeforeChange. In most cases, for example, loading a form, some
fields need to be disable or enable based on the rule, no OnValidation is
fired, so I leave it.
What should I do now? My client cannot bear this kind of performance, if I
cannot change something, we have to select other solution instead of
InfoPath.
ln of manifest.xsn is 2000, ln of view.xsl is 5000.
Regards,
Shen
loading a form needs more than 20 seconds.
I'm using InfoPath 2003 + SP2, and I search from Google and found some
materials, but cannot change much, it still shows very slow.
What I've done are
1, Remove the <xsf:domEventHandlers/>, <xsf:ruleSets/> and use one gobal
OnAfterChange event handler to handler all events.
2, Limit the size of data passed via Web Service.
3, I also want to use C# code to take the place of <xsf:customValidation/>,
but cannot implement it. I've tried OnValidate, but this event fired only
after OnBeforeChange. In most cases, for example, loading a form, some
fields need to be disable or enable based on the rule, no OnValidation is
fired, so I leave it.
What should I do now? My client cannot bear this kind of performance, if I
cannot change something, we have to select other solution instead of
InfoPath.
ln of manifest.xsn is 2000, ln of view.xsl is 5000.
Regards,
Shen