-
Hello
Glad that you got it working
-
Hi Blackhawk,
Yes! There are several best practices:
Don't delete or rename nodes as that will cause schema invalidations and old XMLs won't load
Make sure newly added fields aren't required
If you must make changes that don't meet #1 and #2 above, create a separate form library and save the XSN there
or, you can ...
-
Hi Catharine,
Sorry for the delay in responding. Is the SName field repeating or an element of a repeating group? If so, you'll need to use current() to properly select it. For the secondary data source checks you may need to eval through them since there will be more than one. This will likely require some code. If you were filtering, it ...
-
Hi,
Check out this link,
http://www.infopathdev.com/forums/p/4447/17397.aspx#17397
Hope this helps you.
-
Hi Fabian,
I have no idea. Must be server-side though. Check out your SharePoint database settings.
-
Hi DMU123,
Sorry for the delay in responding. You can create an MSI file. There are several tools on the web that will help you here. You will also need to run some installer code. It's a lot of work to do this. You can easily distribute the InfoPath forms as separate MSIs using the regform tool to create them (see the SDK). For hte database, ...
-
Thanks for the precision.
It seams logic :)
-
Hi Sithender,
For a browser-enabled form, you should use a UDC file for your Active Directory Web service. It should look something like this:
<?xml version="1.0" ?>
<?MicrosoftWindowsSharePointServices ContentTypeID="0x010100B4CBD48E029A4ad8B62CB0E41868F2B0"?>
<?mso-infoPathSolution ...
-
Hi,
When you deploy the form are you deploying it exactly to the same address that the user is using to access the form? For security reasons InfoPath is very particular about the access path for the form. It must be opened using the exact same address as it was published to. This gets encoded into the template at publish time. You have to check ...
-
Hi Bill,
Have you tried putting an OnAfterChange event handler on the parent?