The QuickBooks ADO.NET Data Provider enables user to easily connect to QuickBooks data from .NET applications. Complete read-write access to QuickBooks enables developers to search (Customers, Transactions, Invoices, Sales Receipts, etc.), update items, edit customers, and more, from any .NET application.
QuickBooks
QuickBooks .NET Connectivity Features
- SQL-92 access to local and remote QuickBooks company files
- Compatible with QuickBooks Premier, Professional, Enterprise, and Simple Start edition 2002+
- Supports the Canada, New Zealand, Australia, and UK editions from 2003+
- Connect to live QuickBooks Desktop data, for real-time data access with the QuickBooks Desktop JDBC Driver
- Full support for data aggregation and complex JOINs in SQL queries
- Seamless integration with leading BI, reporting, and ETL tools and with custom applications via the QuickBooks Connector.
Target Service, API
The driver provides access to QuickBooks Desktop versions 2002+ including Premier, Professional, Enterprise, and Simple Start editions. Supports Canada, New Zealand, Australia, and UK editions from 2003+. Works through the QuickBooks SDK and QuickBooks Gateway.
Schema, Data Model
Models QuickBooks data as relational tables with dynamic metadata discovery. The driver exposes QuickBooks lists and transactions as tables, automatically detecting custom fields and providing a SQL interface to QuickBooks data.
Key Objects
Customers, Vendors, Items, Invoices, Sales Receipts, Purchase Orders, Bills, Accounts, Classes, Transactions, Reports, Employees, Inventory, and custom fields. Full access to QuickBooks lists and transaction objects.
Operations
Full SQL-92 operations including SELECT, INSERT, UPDATE, DELETE. Supports complex queries with JOINs and aggregations. Read-write access to QuickBooks data with support for creating and updating transactions. Some operations may be limited by QuickBooks SDK permissions.
Authentication
Connects through QuickBooks Gateway which runs on the same machine as QuickBooks. Requires QuickBooks user authentication. The Gateway uses lightweight embedded web server for connections. Supports authorization when QuickBooks is running or can open QuickBooks automatically with saved company file.
See what you can do with QuickBooks ADO.NET provider
Use QuickBooks from SQL Server Analysis Service (SSAS) multi-dimensional cubes. Keep your analytical data modeling and access to any source including cloud and on-premises.
The QuickBooks ADO.NET Provider allows developers to build applications that connect to QuickBooks using familiar SQL and Entity Framework. Integrate QuickBooks to your mission -critical applications or create easy side-by-side applications.
You can connect from ADO.NET compliant low-code development tools:
You can connect QuickBooks from .NET-based reporting and analytics tools:
Standard ADO.NET Access to QuickBooks
The QuickBooks ADO.NET Provider offers the most natural way to access QuickBooks data from any .NET application. Simply use QuickBooks Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the QuickBooks Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.
The CData ADO.NET Provider for QuickBooks hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Working with DataAdapters, DataSets, DataTables, etc.
The QuickBooks Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: QuickBooksConnection, QuickBooksCommand, QuickBooksDataAdapter, QuickBooksDataReader, QuickBooksDataSource, QuickBooksParameter, etc. Because of this you can now access QuickBooks data in an easy, familiar way.
For example:
using (QuickBooksConnection conn = new QuickBooksConnection("...")) {
string select = "SELECT * FROM Customers";
QuickBooksCommand cmd = new QuickBooksCommand(select, conn);
QuickBooksDataAdapter adapter = new QuickBooksDataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
More Than Read-Only: Full Update/CRUD Support
QuickBooks Data Provider goes beyond read-only functionality to deliver full support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the QuickBooks Data Provider as easily as interacting with a database table.
using (QuickBooksConnection connection = new QuickBooksConnection(connectionString)) {
QuickBooksDataAdapter dataAdapter = new QuickBooksDataAdapter(
"SELECT Id, Where FROM Customers", connection);
dataAdapter.UpdateCommand = new QuickBooksCommand(
"UPDATE Customers SET Where = @Where " +
"WHERE Id = @ID", connection);
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");
DataTable CustomersTable = new DataTable();
dataAdapter.Fill(CustomersTable);
DataRow firstrow = CustomersTable.Rows[0];
firstrow["Where"] = "New Location";
dataAdapter.Update(CustomersTable);
}
ADO.NET Provider Performance
With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:
- Network Connections - Slow network connections and latency issues are common in mobile applications.
- Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
- Large Data - Intentional or unintentional requests for large amounts of data.
- Disconnects - Complete loss of network connectivity.
The CData ADO.NET Provider for QuickBooks solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.
Smart Caching
Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.
Caching with our ADO.NET Providers is highly configurable, including options for:
- Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
- Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
- No Cache - All requests access only live data and no local cache file is created.
This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.
More information about ADO.NET Provider caching and best caching practices is available in the included help files.
Visual Studio Integration & Server Explorer
Working with the new QuickBooks ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the QuickBooks Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, QuickBooks ADO.NET Provider can be used to access and explore QuickBooks Desktop data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to QuickBooks ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the QuickBooks Desktop Data Source
- Configure the basic connection properties to access your QuickBooks Desktop account data.
Explore all of the data available! QuickBooks ADO.NET Provider makes it easy to access live QuickBooks Desktop data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the QuickBooks Desktop Data Source.
- These constructs return live QuickBooks Desktop data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to QuickBooks
Connecting Web, Desktop, and Mobile .NET applications with QuickBooks Desktop is just like working with SQL Server. It is even possible to integrate QuickBooks ADO.NET Provider into applications without writing code.
Developers are free to access the QuickBooks ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.
- Developers can connect the QuickBooks Desktop Data Source directly to form components by configuring the object's smart
tags.
- Add a new Data Connection from the Server Explorer and select the QuickBooks Desktop Data Source. Then, select the
feed, view, or services you would like to connect the object to.
Done! It's just like connecting to SQL Server.
- Once the object is bound to the data source, applications can easily interact with QuickBooks Desktop data with full
read/write (CRUD) support.
Popular ADO Videos:
