-
Have you tried using a wildcard for the fund? If you want the user to be able to search across funds, then why not just build that into your query, either by the user typing a wildcard, or by using custom code to build your query before submitting it.
Greg Collins [InfoPath MVP]
-
Maybe I'm not understanding what exactly you want to do.
When you query, you query in a single set of fields. The query itself RETURNS multiple rows. Those returned rows are populated into the datafields. That is where you do your editing and submitting. The query is only to get the multiple rows into the datafields... not to do the editing ...
-
Sorry, I must have missed that last paragraph on your original post.
One option you have is to create a secondary DOM based off the schema of your data set with the addition of the boolean. Copy the data into the secondary DOM and set the boolean to true. Use the secondary DOM in the view. All new rows will automatically have false for the ...
-
Time consuming is your task now...
Verify that each file is ''valid''... you can use XML Spy or another XML editor, or you can load them into Internet Explorer to see if any errors are present.
Beyond that, the best thing to do would be to create a new project, and then manually copy bits over from each file, testing along the way to make sure ...
-
It's not that difficult of a problem, but will require the addition of a flag attribute on your row. Here's what I have in mind:
You could add a boolean attribute to the repeating rode representing the row. Say the attribute is @new and the default value is true.
When new rows are inserted, the value of @new is true. This is your indicator to ...
-
If you are using InfoPath SP1 you can use a formula as a default value for a field. This formula can do the kinds of operations you mentioned. The value can update automatically when the other fields change.
Greg Collins [InfoPath MVP]
-
I'm curious if in your data source, the dates appear as elements or attributes? If they are elements you should be able to have them nillable in the schema that InfoPath creates. If they are attributes then you are out of luck other than to set them as strings.
If you are using a Web service, you might be able to have dates on the database end ...
-
Sorry. I try to get to these questions, but my time is drawn between many thing, including fulltime work.
Since your datafields are essentially identical, except for maybe a root node or two, what you can do is the following. Let's assume your common root node is named s0:MyData.
var oMyData1 = ...
-
First try deleting your BIN and OBJ folders and then trying to open it again.
If that doesn't do it, take a look at the following thread on Google Groups and see if it helps:
http://groups.google.com/groups?q=infopath+collins+gacutil&hl=en&lr=&selm=eNSvkVMhEHA.596%40TK2MSFTNGP11.phx.gbl&rnum=1
Greg Collins [InfoPath MVP]
-
What you are experiencing is the correct behavior. The query fields are not for data editing and submission, that's what the data fields are for. The query fields are only to ''query'' the database and populate the data fields.
You need to bind your repeating table to the data fields for data entry and submission.
Greg Collins [InfoPath MVP]