InfoPath Dev

It's not that "it's not working" in InfoPath 2007; what you're describing is default behavior in InfoPath 2010! :-) In InfoPath 2010: If you click on a control it'll display that controls properties in the ribbon, at the top. You can click any of the options there to see further options for that field. Or you can right ...

If it's not just the one InfoPath form, then it's probably a SharePoint issue. Maybe some settings or permissions have changed recently, or a patch applied to the server? Anyway, it's worth a shot asking some SharePoint experts if you can get the same error in multiple sites using different InfoPath forms. Good luck.

You will have to modify your form, check the option to browser enable the form, then republish. Why are you unable to republish?

 Does the form have any sensitive data? If not, could you send it to support at qdabra dot com and I'll take a look. I'd verify whether I can reproduce the error on our servers.

Are you doing this via rules and, if so, where are the rules set? The rules you are using to set the value of high/0 must be placed on the control whose value is changing, in this case the field that holds the "180" value. Such that when the value changes from 180 to something else, the rules fire and the other field(s) have their ...

One node in your xml schema can have multiple controls to show its contents in the form, but each control's settings must be configured individually. I would begin by checking that the settings on all the controls match. If they do, please let us know and we'll see what else could be causing this. Good luck.

Out of the box there's nothing in InfoPath to allow that server-side filtering. We have a technique using qRules, documented here, but you could search online for other techniques. Good luck!

The dropdown should have two options: value and display. The "display" is what is shown to users. The value might be that numeric index you are referring to. How is the dropdown configured? You can right click and select Properties to check it and modify it.

Setting the SharePoint form library to open the form in the browser is not enough. You need to also make sure that the form's compatibility is set to browser. You can change this in the form while in design mode, and then run a Design Checker to make sure that there are no issues. Good luck!