-
In the MSDN documentation, it says:
When you use the Open method, the specified form opens in InfoPath and is ready to be filled out.
I don't see any overloads that would let you use that method without opening the form. Searching Google didn't pull up too many alternatives, either. There is a company selling a product that allows you to ...
-
Hi:
When the form is submitted, if you are talking about the little dialog that tells you whether or not it submitted successfully, that can be set in your submit option. I know some warnings can be toggled with IE settings -- which ones are you seeing?
-
Hi:
Does the Qdabra Event Log have any additional information? Does the account you are installing with (default is NT AUTHORITY\NETWORK SERVICE) have the proper permissions in SQL to create databases?
-
So the fields they are filling out -- are those bound to query fields or data fields (this is a databased bound form, is that correct? That is, a form based off a db when first designed?). If they are query fields, my thought would be that your rule is running when they fill out the value and re-querying the data....
-
Hi:
Here's my go-to link for encoding and decoding base 64. Hope it helps!
-
Hi:
Check here for samples and directions on using input parameters. After you have the string variable for your parameter, you should be able to use (C#)
this.ViewInfos.SwitchView(stringvariable);
to switch to the view passed in by your parameter.
-
What happens if you try to simply open the form, instead of opening in design and previewing? The form doesn't have a file specified for use in preview, does it (Tools / Form Options / Preview)? We get a very simple 'The form cannot be opened' error when we try to preview the form and file has been specified that can't be accessed.
-
I don't think you would be able to do this with out of the box InfoPath functionality. I don't believe that Access has triggers -- SQL Express does, I think, and it is free. You might want to consider moving your DB to SQL. Because, really, a trigger would work nicely for creating a history table.....
-
In the DBXLDocumentService web service there is a method called GetAllDocumentTypeSummaries that returns information on who last modified the document type configuration. That won't necessarily tell you who last changed the template, because they could have been modifying permissions or database mapping, but it may be helpful.
-
You don't have to have an 'else' statement. I had assumed you were using that for some kind of debugging? Just remove your 'else' that has the message box with the error. It seems to me that you have decent error handling in your if block -- you return an error if the user isn't in AD or if something goes awry in your try ...