M
Matt
Can anyone explain to me why my OWC pivot table keeps adding in the
NoAllowGrouping and NoAllowFiltering parms whenever I make a simple
change to my ASPX page?
If I add the OWC to my page and build and view it there usually isn't
any problems. If I try to make a change to anywhere in the page (like
insert a carriage return) the OWC rewrites itself and inserts the
NoAllowGrouping and NoAllowFiltering parms. This is very frustrating.
To make it worse, I don't seem to be able to use the "properties"
option in design mode to fix the parm settings. I have to go into HTML
view and delete the parms (<x:NoAllowGrouping/>
<x:NoAllowFiltering/>
) manually.
Any ideas? I'm using VS2003 (this problem existing in VS2002 also) so
it can't be an editor bug.
NoAllowGrouping and NoAllowFiltering parms whenever I make a simple
change to my ASPX page?
If I add the OWC to my page and build and view it there usually isn't
any problems. If I try to make a change to anywhere in the page (like
insert a carriage return) the OWC rewrites itself and inserts the
NoAllowGrouping and NoAllowFiltering parms. This is very frustrating.
To make it worse, I don't seem to be able to use the "properties"
option in design mode to fix the parm settings. I have to go into HTML
view and delete the parms (<x:NoAllowGrouping/>
<x:NoAllowFiltering/>
) manually.
Any ideas? I'm using VS2003 (this problem existing in VS2002 also) so
it can't be an editor bug.