-
Well, everyone here was new at some point!
You don't have to have a control on the form that is bound to the approved field in the data source, as long as the field is in your data source.
Is your form built off the table? That is, when you designed your form, did you select to design it off a database?
If so, your main data source for ...
-
Well, I'm going to guess that your form was created off your database. If that's the case, it isn't set to query on open.
I did a simple test. I created a form off a database, and then, I created an open rule that sets the data source query field for ID to the same value as the data source data field for ID. Then I added an action to ...
-
Hi, Jeff:
Have you considered using User Roles? You could set up a role for supervisors, and add some controls to the timecard that would be hidden if a person wasn't a member of that group. You could create another view of the timecard that was read-only, and add an open rule that would switch to the read only view if the timecard was marked ...
-
It is feasible -- Jimmy's post above has the gist of the matter. You'll need to do the following:
Save your form as source files
Find the main schema (.xsd) file for the form (default is 'myschema.xsd')
Modify the schema to include an xsd:any node where you want to be able to add elements
Open the manifest.xsf in design mode and ...
-
Well, actually, there is a pretty big difference between yours and the sample. In yours, you have an element called Funding. If you want the element of funding to have the value of 'No', it would look like this:<Funding ChequeValue="Under 500" AuthBy="Adrian Grant">No</Funding>
Notice that there is no ...
-
Then instead of using rules for your submit options, set rules on the DDL. One action you can chose is to submit a form. Again, you can use conditions here -- if 'a', then submit using one data connection, if 'b', use another.
-
I would use rules for my submit. I'd set the rules with conditions -- so, for example, if the DDL value was 'A', you'd use one submit connection to submit the form and if the DDL value was 'B', you'd use another. Make sense?
-
That makes it less straightforward, then, and you'll probably need code. I've not written anything to export to Excel -- hopefully someone else on the forum has and can contribute some knowledge on that.
I did find a blog post with a sample for using managed code to submit data to an Access DB that may be of some help: ...
-
Hmmm.... If your form schema is fairly flat (no repeating items), you could always promote all the columns and create a linked Excel spreadsheet or Access database....
-
Hi there -- try pasting the xml into a simple text editor, like notepad, and saving it with a .xml extension. In fact, I'll attach a copy to this post for you, so you can just right click the link and select 'Save As' to get a copy.
Hope that helps....