InfoPath Dev

Imagine that your InfoPath form, which submits to DBXL, needs to make sure that there are no duplicate records. Using the web method QueryDocumentNodeSet, we can quickly check whether DBXL already contains...

Every document created in DBXL will be assigned two identifiers: the RefID and the DocID. This document explains the difference between the two.

If you encounter errors in the xref tables in DBXL, this document will explain how to identify and address these. Click DOWNLOAD above to obtain this document. To obtain a trial version of DBXL, please...

Sometimes we need to know the DocID for an xml documents that was just submitted to DBXL. For example, we might want to send an email with the link to the submitted document. This document will guide you...

In order to see previous versions of forms, you’ll first need to check the Enable History option in the Database tab in Qdabra’s DBXL Administration Tool. Click DOWNLOAD above to obtain a document with...

DBXL versioning is turned on by default, as it is necessary for certain scenarios. For safety purposes the checkbox in DAT is also disabled, so that it is not accidentally deactivated. However, should...

Deploying full trust templates in DBXL requires some additional steps, which are documented in this attachment. Click Download to obtain this.

Every document created in DBXL will have a unique DocID. Typically we refer to documents stored in DBXL by using their DocID. However, every document also has a RefID. In this tutorial we will discuss...

In DBXL, there is a DocumentStats table that stores a log of the locks, unlocks, and saves of each document. This document contains a reference table for these keys. Click DOWNLOAD above to obtain the...

This is a .NET library for use in interacting with DBXL from .NET code. See the following blog post for more details: http://www.infopathdev.com/blogs/jimmy/archive/2012/09/18/interacting-with-dbxl-from...