-
You should be able to use the SaveAs() function inside a custom submit procedure, but saving to the local hard drive will require full trust.
-
You could do this by editing the template.xml file, or with code in the OnLoad event.
Editing the template.xml would entail simply adding the appropriate xml to display by default. In this case it would be five instances of the row that you are talking about. To get at the template.xml if you are not using managed code choose Extract Form files ...
-
Hi Brandt,
I'm not sure what is causing that error, but I think it has something to do with not having the proper libraries installed. Like I said, it worked for me so maybe it was packed with my installation of Visual Studio. Maybe someone else has had the same problem, I would consult Google.
-
Sounds like you don't have something installed. I'm not sure what your development environment is, but the ADO stuff installed itself for me.
Try downloading and installing this:http://www.microsoft.com/downloads/details.aspx?familyid=5067faf8-0db4-429a-b502-de4329c8c850&displaylang=en
-
Shaul, I don't think this can be avoided. However, you might look into using mutliple views on one forms instead of several XSN files if you are accessing the same data source.
Just a thought.
-
You could probably do this easier with data filtering on the drop-down list.
Either way you will have to populate the drop-down from a secondary data source, once this is done you could add/remove rows with code or use the better option of data filtering on the drop-down control.
To add data filtering, click the ''Filter Data'' button when ...
-
Hi Brandt,
In exploring this issue I used the AdventureWorks database that comes as an example with most installations of SQL. I called the following stored procedure to retrieve two output parameters:
USE AdventureWorks;
GO
IF OBJECT_ID ( 'Production.usp_GetList', 'P' ) IS NOT NULL
DROP PROCEDURE Production.usp_GetList;
GO
CREATE PROCEDURE ...
-
I think you will have to store the project ID in each of the rows, then you can do filtering and conditional formatting on it.
-
Probably something like this:
XDocument.DOM.selectSingleNode( ''/my:myFields/my:textboxField'' ).text;
Hope this helps!
-
Hi Will and welcome to the forum!
I am sure Excel would be the easiest to convert to XML. I just tried saving a worksheet as an XML Worksheet via File -> Save As -> XML Spreadsheet. After you do this, you should be able to add this XML document to your InfoPath form as a secondary data source and then populate from there. Even better ...