InfoPath Dev

DBXL Version: 2.6.2012.324 Form Version: 2.6.0.153

Thanks this fix worked. But now I noticed that when fields are promoted in InfoPath, they are first created when published from SharePoint. Then a duplicate set of fields are created in the InfoPath Library when the form is published again from Qdabra. How do I prevent this?

I created a form that maps its fields to a DB. I save it and publish it to SharePoint using DAT. It opens fine. But when I update the XSN template with a SharePoint List data source and save it using the DAT. I get an error. In the InfoPath Client I get an the below error. Thank you in advance for your help.  "The form cannot be ...

Thanks for your quick response. You mention a "document". Which document is that?

I noticed when I first started using the DBXL Admin Tool, there was a minor delay after clicking OK on the "Changes Saved" dialog box after saving a configuration change. As I've added more fields (300+ now), the DBXL Admin Tool is frozen for about a minute or two. Is there something I can do to avoid this delay?

It looks like you're adding the local "Everyone" group to have permission to write to the Qdabra Event Log. Looks like it worked. Thanks.

Currently I have a problem with updating an InfoPath template using the DBXL Admin Tool. I have the Qdabra Web service installed on a SharePoint WFE to utilize the SharePoint Object Model. I am able to configure a new InfoPath library by using the "Publish Library and XSN" and "Use Forms Services" checkbox. But when I attach an ...