-
I do understand the difference between a relative and absolute path -- but as I said in my response, I don't know what the syntax would be for a relative path to a DB in InfoPath...
The template uses relative paths to its resource files.... I wonder if you could add your DB as a resource file? Instead of having it in your folder with the ...
-
I'm not sure what the relative path would be for this, or if this would work -- but I question the design decision. Do you really want a copy of the Access DB with the form? Then every user has their own DB?
Wouldn't you want the DB on a network location instead?
-
You'll see from the MSDN link I referenced that:
For secondary data sources, the WebServiceAdapter object is accessible through the QueryAdapter property of the DataObject object, and DataObject objects are accessible through the DataObjects property of the XDocument object.
The code sample shows that you'd want:
set dataObj = ...
-
Hi and welcome --
It would be helpful to know what version of InfoPath you are using. For 2007 and above, you can right click a field or group in the data source task pane and select "Copy XPath" to get the XPath to a node.
According to MSDN, the WebServiceAdapter has been with us since IP 2003. The line of code you get the error on ...
-
I'm guessing we are cross posting a bit -- to clarify the first sample does not use qRules, but default values and a manual manifest change.
The second sample uses qRules.
So now you have two choices!
-
Well, to use qRules, you'd need take the approach outlined in this document. Basically, you'd have to insert into your main data source the number of groups you need, then you can use a counter field to loop through and set values. Since the counter will move from n to 0, the items may be in the opposite order you expect, but you can ...
-
The translate function is removing the "-" from your dates, so that the dates are numbers like 20110301 or 20110809. Now the operator ">" knows what to do, since you are comparing two numbers....
-
This thread may help you. And here's some code samples for IP 2003 and 2007. You'll want to set your Boolean to "true", not "True", however. XML being so darn case sensitive and all. The code sample for IP 2003 is jscript, but should give you the general idea.
-
This MSDN link may help you. Just add a secondary XML data source to your form, and have a node in it that you set to your error message. Display the node on the form when it has a value. Add some logic to clear the error -- maybe an "OK" button on the form or something.
-
I think Jimmy is suggesting you use this in place of your current rule (which from your post sounds like conditional formatting on the date field).