-
Just add a repeating group or fields, depending on your need, to your main data source. Right Click on the node.
-
Hi Jeff.
Send me an email and I can show you a way better way of doing this, overcoming the default limitations, with web services.
-
Hey Jeff.
Typically you would just leave these "legacy fields" in your data source and just remove them from your views. Since if you remove them the old forms are then broken. Unless this is a large amounts of fields there is no real reason to eliminate these old fields from the datasource. No one would know unless they were in ...
-
Max is used on a repeating node to return the largest value from the list. Since these are two fields you need to think simpler.
In your case you would have two conditional rules a>b and b>a and then have your action, maybe set max with value of a if it is greater, etc.
-
What does the check box do?
When they select it?
Often I would have a rule on the checkbox that when it is selected it use a setfield action to copy the cooresponding list data into your main form.
Then this selection will be saved or could be accessed later.
This is compatible with form services.
-
If you would like to see how to add web services to your SQL server and give yourself a lot more possibilities and functionality send me an email and I can show you some examples.
-
It really kind of depends on the data and the form flow.
The simplest way is to use a set field action.
The most complex is using code to copy a whole node.
Give a bit more detail of what you are wanting or a screen shot.
-
Yes if this is from one server or site to another you would need to reconfigure all of your DCs to point to the lists or libraries on the new site. The GUIDs must be set for it to work.
-
It sounds like you are not storing the values in your main data source. The fields for the check boxes should be bound to fields in your main data source if you want them retained.
Typically you would load the secondary data but then transfer it to your main data so that the responses can be stored in the form and be used later.
-
Hi Dawn.
Sorry to hear of these issues. I have seen similar issues before in multi-user environments with Access.
Unfortunately I believe this is an Access issue. Access is really not designed for this kind of utilization. Its performance as well as network and client performance could all contribute to these inconsistent types of ...