InfoPath 2013 vs InfoPath 2010 (Data source compability issue) - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

InfoPath 2013 vs InfoPath 2010 (Data source compability issue)

Last post 08-08-2015 03:01 AM by kromeda. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 08-08-2015 03:01 AM

    InfoPath 2013 vs InfoPath 2010 (Data source compability issue)

    Hello, at first I would like to apologies for my English, I’m working on it. I’v got a problem, when I created an InfoPath 2013 Filler Form and added secondary data source with an MS Access table. I left "automatically retrieve data when the form opens" selected. Everything is going to be fine until someone with an InfoPath 2010 installed trying to open it. I set option in properties of the form, so it’s comparable with InfoPath 2010 (also i tried "Empty Form 2010 (InfoPath FIller)" from scratch, and got the same result). Anyway, when person with InfoPath 2010 try to open it will get connection error (cannot query table (secondary data source) or smth) during Form load, and it will open without data stored in tables. I tried to find out what’s the problem. And here’s what I found: by default, when you add MS Access database table as secondary data source Form defines to it OLE DB provider, and there are some particular properties for connection string to every MS Access connection. For example Provider=Microsoft.ACE.OLEDB.12.0; Password=””; User ID=Admin; Data Source=D:\Shared\BD\reading.accdb; Mode=Share Deny None; Extended Properties=””; Jet OLEDB:System database=””; Jet OLEDB:Registry Path=””; Jet OLEDB:Database Password=””; Jet OLEDB:Engine Type=6; Jet OLEDB:Database Locking Mode=1; Jet OLEDB:Global Partial Bulk Ops=2; Jet OLEDB:Global Bulk Transactions=1; Jet OLEDB:New Database Password=””; Jet OLEDB:Create System Database=False; Jet OLEDB:Encrypt Database=False; Jet OLEDB:Don't Copy Locale on Compact=False; Jet OLEDB:Compact Without Replica Repair=False; Jet OLEDB:SFP=False; Jet OLEDB:Support Complex Data=False; Jet OLEDB:Bypass UserInfo Validation=False; Jet OLEDB:Limited DB Caching=False; Jet OLEDB:Bypass ChoiceField Validation=False This information is available from the manifest.xsf file. Connection string was built within InfoPath 2013 Form. The same connection string properties are present for InfoPath 2010, except two last properties. These are the core difference between IP 2013 and IP 2010 connection string when you add secondary data source with MS Access DB table. In IP 2010 these properties are simply not provided. There are no even space for them if you try to “create” connection in a data connection wizardry (InfoPath 2010) and press “Choose data base” -> “Create” -> “Additional” -> “Microsoft Office 12.0 Access Database Engine OLE DB provider” -> tab “All”. For me solution was to use ODBC data provider instead of OLE DB, but I don’t really think Microsoft could allow such issue with compatibility of InfoPath 2010 and InfoPath 2013
Page 1 of 1 (1 items)
Copyright © 2003-2018 Qdabra Software. All rights reserved.
View our Terms of Use.