-
You got that error figured out on MSDN, right? Does everything open fine in the browser now?
-
Alec, it does have far more, and it does not get installed to the server. It's just a local installation, and you inject to your own forms. The only administrative interaction would be if you use qRules for browser forms. There are at least 6 qRules in 1.7 that I will be using regularly, and the others I just haven't ...
-
Yes, all of that info is critical to resolving the issue, so thank you for adding. What you've described sounds very doable and is in fact something I am doing currently with a pretty dynamic form, except I am not asking for comments upon rejection - that is all handled in person instead of through text, but it's certainly a ...
-
Yes, as Hilary mentioned, you'll need to use some piece of the user's identity to compare against a value in each row and then use conditional formatting to make those other rows read-only. It's very easy to do as long as you have a value to match.
-
Yes, that's the whole point of browser-enabled forms. It's a function only of InfoPath 2007, and it requires MOSS Enterprise (includes Forms Services) or MOSS Standard plus Forms Server (separately-installed product). It's most typical for organizations to use MOSS Enterprise for full browser-enabled forms ...
-
Buttons don't have values, so what do you mean when you say you're passing a value to it? Do you just mean you are setting a value in the Dummy and then basing the button's conditional formatting off of the Dummy field?
-
You should definitely be talking directly with your MS rep who you do business with for your enterprise agreement or whatever it is your company has for Office. It's all usually bundled up into one agreement so that your costs aren't full retail, and then you have to work with them to determine the best licensing for your ...
-
You have to make a static width, unfortunately, so it's up to you what width works best for everyone.
-
It's relevant to their screen resolution and size of the window. You need to set static widths for your fields in the form template, else they will auto-expand like that. IT's a pain, but it's a known issue (not just your issue).
Not sure about the skewed colors.
-
Not sure of a trick for that other than to use the IsDirty qRules that Qdabra has in version 1.7. 1.6 is available for download right now from this site, but 1.7 will be available later this week. You can check for data validation and use it to disable the button (or any other control). I have already verified that this works and ...