InfoPath Dev

 This thread might help: http://www.infopathdev.com/forums/p/15172/53778.aspx#53778

We have been able to reproduce the issue. More info soon...

Hi Tobias, I don't have a fix at the moment, but we'll investigate. Thanks.

Thanks for the info. It's interesting that the error doesn't show in SharePoint 2010! In SharePoint 2007, we've seen some customer environments where Object Model refuses to work. When they switch to Web Service, the SharePoint mapping works nicely. Can you try that? If you encounter any other errors, please take screenshots and, if ...

 Does this issue happen in both SharePoint 2007 and SharePoint 2010?

Hi infopathman, Is this an IPFS form? My memory is a little vague, but I remember working with an browser form (no Qdabra products involved) where locking was not respected by Sharepoint itself, and users could overwrite each other. I would need to recreate the scenario to confirm. But anyway, to get to the bottom of this, what does your submit ...

Hi infopathman, Nice job of figuring this one out. Hopefully it'll help others in the future. One final question: what does your submit button do? Does it submit via the DBXLDocumentService? If so, I'd like to move this post to the Qdabra DBXL forum. The Active Directory Web Service doesn't have a submit operation, so it's a ...

The Getting Started guide aims to quickly expose a new user to the basic functionality of DBXL. The goal is to give new users a quick, step-by-step tutorial covering basic functionality, but without drowning in too much information. After becoming comfortable with Getting Started, you can continue building on your DBXL experience with other ...

Hi, The xml data needs to be submitted/stored in DBXL so that it can be then mapped into SQL. This means that the form cannot be published to SharePoint from InfoPath; DBXL needs to 'publish' the form to SharePoint via DAT (to retain "ownership" of the xsn). I believe this is covered in Getting Started, but the following ...

Don't feel bad. I don't think it's a newb mistake (and, even if it is, we all make them, we're all newbs at one point); but I would like to get to the bottom of it so we may help other customers in the future. :) The name of the XSN doesn't need to match the name of the Document Type. That shouldn't be the issue. Perhaps ...