InfoPath Dev

I originally began development of my infopath form in 2007; however, the new development environment that I have only has 2003.  When I open my form in design mode, many but not all, of my views are showing as "(protected)".  I am unable to even select the view.  Does anyone have any advise on what setting could be causing these views to show as protected?

IP07 supports features and XSL constructs not available to IP03. I'm assuming that you exported your 07 form template to 03 so that you could develop in 03.

The "protected" bit is a little-known feature that InfoPath supports which allows you to design your own custom XSL views outside of the designer and have them used in the form template. There is an attribute on the xsf:view element in the manifest.xsf file which determines whether a view falls into this protected category. The attribute is designMode="protected".

If you remove this attribute from the xsf:view element, you will be able to open the view in the designer. However, if there are unsupported constructs or features, those will be lost when you make changes to that view. So make a backup copy of your form template before attempting the attribute removal.

Thanks Greg!

 I am assuming this designMode value was set to protected b/c I used functionality that was available in 07 and not in 03.  I found the functionality on a drop down list - a check box to display unique display names.  After ensuring that all the fields didn't have this checked, I was able to go back to my 03 environment and access the views. 

 I was surprised that this was not caught in the design checker since there is the option to show compatibility with 2003.

Technically, that should not have caused an issue. It's simply a filter and those are supported in IP03 if it is on the main DOM. If its on a secondary DOM, then that might be an issue.

It was a secondary DOM

Now you can still use filters on secondary dom controls, however you must do them manually in the XSL in InfoPath 2003. For some reason that feature was disabled for secondary data sources--even though filters are fully supported.