-
Or you might try the ''Local Intranet'' zone - that's what we have all of our users add the site to and this is the answer to a large number of support problems.
-
You might need to make two controls: one regular, and one specifically formatted for when the control is disabled. Then on the conditional formatting you can show/hide the controls on the same condition that performs the disabling.
-
You should be able to do this from the designer. Add custom data validation so that if the length of the current field is equal to zero, then it is invalid. I don't think you should be digging around in the XSD unless you absolutely have to.
-
I'm still confused on how the xml file is being updated. Below is the new hire form workflow.
H/R initiates the new hire form. Email the form to the hiring mgr as an attachment using the new employee name as the attachment name. I have added a rule to close the form so it prompts the user wants to save the form. If the user save the form ...
-
This does not appear to work. It appears that it is treating each line as an 'AND' and not an 'OR' so unless all of the validations resolve to true the field is not required.
-
Hi all,
I've been reading a lot about the difference between not required and optional, and I thought I understood it, but my form seems to disagree.
I have some elements that are strings that I would like to make required (meaning they better be filled) from the schema if possible. I have this in my schema:
<xs:element name=''someName'' ...
-
Hi Deborah,
Whenever you want to change the length of the field, if increasing the length of the field size then no problem but you are decreasing the size it will shows the warning message. If you want to decrease the length of the field you need to change the existing data also minimum otherwise it will accept the data up to 300. You need to ...
-
Hi scottr Welcome to the Forums,
In VBScript you should not declare type of the parameter for calling of the function. Have you get the WebService adapter in VB Script? Can you explain me what is the error you are getting exactly
-
I've just verified that this issue did not occur on another machine.
The difference between the two machines? -
- The machine that it works on has only InfoPath 2003 SP1
installed + infopath toolkit + VS 2005
- The machine that it does not work on (i.e. it gives the problem as described above) has InfoPath 2007 beta installed in addition ...
-
No, I didn't make any changes to the view. Just selected the same schema after clicking ''Design form from a Xml Document and/or schema'' and then previewed the form after completing the wizard.
Any ideas?
I've faced this problem even with a simple schema such as the one below.
<?xml version=''1.0'' encoding=''utf-16''?>
<xs:schema ...