Use our Google Custom Search for best site search results.
Search
-
The Qdabra Database Accelerator (DBXL) can be downloaded fromhttp://www.qdabra.com/categories.asp
-
InfoPath does not support accessing the headers, but you can add a web reference to your InfoPath form in Visual Studio and call within your form code.
This is a sample using a webservice defined method with
MyWebService.Auth hdr = new global::InfoPathProject2.MyWebService.Auth();
hdr.Username = ''Fred'';
hdr.Password = ...
-
'thisApplication' is assigned inside the _Startup method which is generated when you create a new InfoPath project.
public void _Startup(Microsoft.Office.Interop.InfoPath.SemiTrust.Application app, XDocument doc)
{
thisXDocument = doc;
thisApplication = app;
// You can add additional initialization code here.
}
-
The download has been updated to include the documentation. You can download the documentation separately usinghttp://qdabra.com/free/qdabraDatabaseAccelerator_v2.0Beta_Developer_Docs.zip
-
InfoPath is not required on the server.
Adding the server to your Local Intranet zone in IE should fix the problem. Once added to your Local Intranet zone, close IE and InfoPath and then try the DAT form again.
-
You will need to reinstall to the WSS v3 site, or another site which is enabled.
-
There is an InitializeDatabase method on the AdminService page which needs to run.
In the IIS manager, check the ASP.NET page for QdabraWebService. It should be using version 2.0.50727.
-
Are you saying that the urlhttp://servername/QdabraWebService/DbxlAdmin.asmx gives you a Sharepoint message?
This link should give you a page titled 'AdminService'.
-
The web.config is additive. All the entries in the parent will apply to the child. Add the following to your ADService web.config (put the <httpModules> section under the existing <system.web> section
<system.web>
<httpModules>
<remove name=''EnterpriseInitializationModule''/>
<remove ...
-
Have you tried editing the ADService web.config to remove BP from just the ADService? You should locate the remove under the same node hierarchy as the add in the parent web.config.
<remove name=''EnterpriseInitializationModule''>