Problem Description:

I would like to import data from Microsoft Excel to QuickBooks. I do not have expertise in programming languages. I have Visual Code (VS Code) and Claude Code. How shall I import the data?

Solution:

Automate importing data to QuickBooks!

In this tutorial, we look at how to automate the process of importing customer data from an Excel spreadsheet directly into QuickBooks Desktop using the power of the QODBC Driver and Claude Code.

Manually entering hundreds of customers can take hours and is prone to typos. By leveraging Claude Code to write our SQL queries and QODBC to bridge the gap between your data and QuickBooks, you can complete this entire process safely and accurately in just a few minutes.

Whether you are an accountant, a business owner, or an IT professional, this step-by-step guide will help you eliminate manual data entry and streamline your data management.

What You Will Learn:

• How to use Claude Code to generate accurate SQL INSERT statements for QuickBooks/QODBC and generate a PowerShell Script.
• Connecting to your QuickBooks company file using the QODBC Driver.
• Automated execution of the PowerShell Script to import the data.

Please ensure the Excel sheet column name matches the QODBC table field name. 

QODBC Table Schema: https://doc.qodbc.com/qodbc/usa/TableDetails.php?tableName=Customer

Sample/Dummy Customer Excel file can be downloaded from the following link: Click Here 

Prompt.

Start of the prompt for Claude Code

================================================================

Use ODBC DSN "QuickBooks Data" and insert the rows from the current sheet "Sample Customers.xlsx" to QuickBooks.

For mapping the fields available in QuickBooks, refer to the QODBC documentation website. https://doc.qodbc.com/qodbc/usa/. QODBC is installed, and "QuickBooks Data" is configured.

Check if the customer name already exists; if it exists, skip.

Generate a PowerShell script file for inserting data from the current sheet "Sample Customers", into QuickBooks.

Use standard SELECT and INSERT SQL statements instead of parameterized statements.

Execute the required command to insert data from the Excel sheet to QuickBooks.

Generate a mapping of fields based on QuickBooks Customer fields (based on QODBC docs https://doc.qodbc.com/qodbc/usa/TableDetails.php?tableName=Customer) and the Excel file/
When generating the insert statement, ignore the QODBC fields that are not mapped in Excel.

Show the process of the import on the console.
Execute the PowerShell script to insert the records.

 ================================================================

End of the prompt for Claude Code

 Keywords: Automation, Artificial Intelligence, AI, AI Tool

Problem Description:

I would like to import data from Microsoft Excel to QuickBooks. I do not have expertise in programming languages. How shall I import the data?

Solution:

Supercharge your QuickBooks workflow!

In this tutorial, we look at how to automate the process of importing customer data from an Excel spreadsheet directly into QuickBooks Desktop using the power of the QODBC Driver and Microsoft Copilot.

Manually entering hundreds of customers can take hours and is prone to typos. By leveraging Microsoft Copilot to write our SQL queries and QODBC to bridge the gap between your data and QuickBooks, you can complete this entire process safely and accurately in just a few minutes.

Whether you are an accountant, a business owner, or an IT professional, this step-by-step guide will help you eliminate manual data entry and streamline your data management.

What You Will Learn:

• How to use Microsoft Copilot to generate accurate SQL INSERT statements for QuickBooks and generate VBA Code.
• Connecting to your QuickBooks company file using the QODBC Driver.
• Executing the VBA Code to import the data.

Please ensure the Excel sheet column name matches the QODBC table field name. 

QODBC Table Schema: https://doc.qodbc.com/qodbc/usa/TableDetails.php?tableName=Customer

Sample/Dummy Customer Excel file can be downloaded from the following link: Click Here

Prompt.

Start of the prompt for Copilit

==========================================================

Use ODBC DSN "QuickBooks Data" and insert the rows from the current sheet "Dummy Customers" sheet to QuickBooks.

For mapping the fields available in QuickBooks, refer to the QODBC documentation website. https://doc.qodbc.com/qodbc/usa/. QODBC is installed, and "QuickBooks Data" is configured.

Check if the customer name already exists, if it exists, skip.

Generate VBA code for inserting data from the current sheet "Dummy Customers" to QuickBooks.

Use standard SELECT and INSERT SQL statements instead of parameterized statements.

Execute the required command to insert data from the Excel sheet to QuickBooks.

Write a VBA Script and execute the VBA script to insert the records.

Generate a full mapping template for all QuickBooks Customer fields (based on QODBC docs https://doc.qodbc.com/qodbc/usa/TableDetails.php?tableName=Customer ).

==========================================================

End of the prompt for Claude Code

  Keywords: Automation, Artificial Intelligence, AI, AI Tool

Overview

This guide provides step-by-step instructions for registering an application on the Intuit Developer Portal and obtaining the API credentials (Client ID and Client Secret) required to integrate with QuickBooks Online. Following these steps will allow your application to authenticate with Intuit's OAuth 2.0 framework and interact securely with QuickBooks accounting and payment data.

The registration process consists of three major phases:

• Creating a Workspace (organizational container for your apps)
• Creating and Configuring an App within the Workspace
• Completing the Compliance Questionnaire to unlock Production credentials

Prerequisites

Before proceeding, ensure that the following requirements are in place:

• An active Intuit account with valid login credentials
• A registered company or business entity (used during workspace setup)
• Your application's technical details ready, including:
  • Host domain URL - qboconnect.qodbc.com
  • Launch URL - https://www.qodbc.com/links/qodbconlineconnectinfo.htm
  • Disconnect URL - https://www.qodbc.com/links/qodbconlinereconnectinfo.htm
  • Redirect URI(s) - https://qboconnect.qodbc.com/clientkey/callback.php
  • Privacy policy URL - https://qodbc.com/privacy-policy/
• Access to the Intuit Developer Portal at https://developer.intuit.com

Part 1: Sign In to the Intuit Developer Portal

Open a web browser and navigate to https://accounts.intuit.com/. Enter your credentials and click Sign In.

Navigate to https://developer.intuit.com/workspaces. This is the central hub where you manage all your developer workspaces and applications.

Part 2: Create a New Workspace

A Workspace is an organizational container that groups applications together and stores business information for compliance.

Click the + (plus) button. This opens the Create a workspace landing page. Click Get Started.

Provide a descriptive name (e.g., "Acme Corp Integration Workspace") and click Next.

Enter your legal company name and address. Ensure this matches official records for the compliance review.

Fill in the contact name, email, and phone number for developer alerts.

Click Open Workspace to enter the dashboard.

Part 3: Create a New Application

Click the + (plus) button inside the workspace and click Get Started.

Enter your product name (e.g., "Acme Accounting Sync"). Avoid using "QuickBooks" or "Intuit" in the name.

Select com.intuit.quickbooks.accounting or payment as needed. Click Done.

Review the summary and click Confirm.

Part 4: Retrieve Development API Credentials

Click Open App to access settings and credentials.

Select Keys and credentials from the left sidebar.

Toggle Show credentials under Development to copy your Client ID and Client Secret.

Part 5: Complete App Details for Production Access

To unlock Production credentials, complete the Settings sections: Basic Info, App URLs, Terms of Service, Categories, Geolocation, and Accepted Connections.

Part 6: Complete the Compliance Questionnaire

Submit the Compliance assessment to evaluate security and data handling.

Click Compliance in the sidebar and select Start questionnaire.

Shortcutting the Questionnaire

If applicable, selecting the 5th checkbox in the first question of App Information may allow you to skip certain sections by answering only two key questions regarding instructions and Re-CAPTCHA.

Part 7: Verify Redirect URIs and Retrieve Production Credentials

Ensure your Production Redirect URIs use HTTPS and point to your live server.

Once approved, return to Keys and credentials to find the unlocked Production section.

Part 8: Configure Your Application (QODBC Example)

Navigate to: Start > QODBC Driver for QuickBooks Online > Configure 64-Bit > System DSN > QuickBooks Online Data > Configure.

Troubleshooting

• Production Locked: Ensure all App Details sections are saved and the questionnaire is submitted (not just drafted).
• OAuth Errors: Double-check for Redirect URI mismatches (including trailing slashes).
• Invalid Credentials: Verify you aren't using Development keys in a Production environment.

Problem Description:

I would like to purchase a new QuickBooks 2024 standard license - no subscription.

Solution:

 Businesses that need new or extra licenses for QuickBooks Desktop Pro Plus 2024 can purchase them from resellers or trusted marketplaces.

One option is the StackSocial deal for a 1-user Windows license:

https://www.stacksocial.com/sales/intuit-quickbooks-desktop-pro-plus-2024-1-user-for-windows-lifetime-license

Once purchased, you’ll receive a license key and product number used to activate the software during installation.

Problem Description:

I would like to know when my QODBC subscription will expire.

Solution:

You can check the status using the QODBC Setup Screen. 

Navigate to Start >>  Configure 32-bit QODBC Data Source

Switch to "Machine Data Source"

Select "QuickBooks Data" DSN

(If you are using QODBC Online, Select "QuickBooks Online Data", for QODBC POS, select "QuickBooks POS Data")

Click the "Configure" Button.

Switch to the About tab.

Click the "Subscription Details" button to know about the registered email address, invoice number, and subscription end date.

Alternatively, you can also check the status of your subscription using the FastSpring website.

Please visit the following link: https://flexquarters.onfastspring.com/account

Input the email address associated with your license.

Check your email inbox, and you should receive an email with the subject:

<Your Fullname>, here is a link to manage your orders

From: FastSpring Checkout <mailer@fastspring.com>

Click the link received to manage your account.

The link (URL) should look like https://flexquarters.onfastspring.com/account/somerandomtext.

Click the "Subscription terms" link to get details about your subscription.

Click the Manage icon and then click Performa Invoice. 

Tags: QuickBooks Online, QBO, Subscription QODBC Online, details subscription, subscription end date. Manage my Account

Problem Description:

I want to get copies of invoices.

Solution:

Proforma Invoice

Please visit the following link: https://flexquarters.onfastspring.com/account.

Input the email address associated with your license.

Check your email inbox, and you should receive an email with the subject:

<Your Fullname>, here is a link to manage your orders

From: FastSpring Checkout <mailer@fastspring.com>

Click the link received to manage your account.

The link (URL) should look like https://flexquarters.onfastspring.com/account/somerandomtext.

Click the Manage icon and then click Proforma Invoice.

The Proforma invoice will be generated and will be opened in a new tab.

Please ensure you click Allow pop-up so that a new tab can be opened.

Past Invocies:

Please check your email inbox for Invoices received from FastSpring.

If you need any specific Invoice that you are unable to find in your mailbox, please email us the following details.

Your Order ID:  or QODBC CDKEY:

Product Name:

Invoice Month:

Please raise a support ticket and submit the requested information.

https://support.flexquarters.com/esupport/index.php?/Tickets/Submit

Tags: QuickBooks Online, QBO, Subscription QODBC Online, Cancel subscription

How FQSaveToCache Works

The process involves a sequence of INSERT statements for the line items of a transaction, with the FQSaveToCache flag controlling when the data is sent to QuickBooks.²

1. Caching the Lines (FQSaveToCache = 1 or TRUE)

• For the first line item INSERT statement, and all subsequent intermediate line items, you must set the FQSaveToCache value to 1 OR TRUE

  • Action: When QODBC sees this value, it takes the data from the INSERT statement and stores it locally in a cache specific to your current QODBC connection.

  • Result: The data is not yet written to the QuickBooks company file.

• Example (Conceptual):

  SQL

   

  INSERT INTO "InvoiceLine" (...) VALUES (..., 1) -- First line, cache it
  INSERT INTO "InvoiceLine" (...) VALUES (..., 1) -- Second line, cache it

2. Finalizing and Writing the Transaction ( FQSaveToCache = 0 or FALSE)

• For the last line item INSERT statement for that transaction, you must set the FQSaveToCache value to 0 OR FALSE. If you do not include FQSaveToCache field and value in the insert statement, it will be considered as FQSaveToCache =0

  • Action: When QODBC sees this value, it performs two main steps:

    1. It combines the data from this final INSERT statement with all the previous cached line items for the same connection.

    2. It sends this complete, combined transaction (header and all lines) as a single batch to QuickBooks via the QuickBooks SDK.

  • Result: The complete transaction is now permanently saved in your QuickBooks company file.

• Example (Conceptual):

  SQL

   

  INSERT INTO "InvoiceLine" (...) VALUES (..., 0) -- Final line, write all cached lines + this line to QuickBooks
  

Problem Description:

I need a list of all joins for QuickBooks tables

Solution:

QuickBooks tables are designed around two primary joining patterns: Header-to-Detail (linking a transaction to its line items) and Transaction-to-List (linking a transaction to its associated master records).

The joins are primarily made using unique QuickBooks identifiers: TxnID for transactions and ListID for master records (like Customers, Items, Accounts).

Transaction/Detail-to-List Joins (Linking to Master Records)

These joins link transaction or line item tables to List tables (e.g., Customer, Item, Account, Vendor) to retrieve descriptive names and details.

The convention is to join a RefListID field (found in the transaction or detail table) to the corresponding ListID field in the master table.

These “Relations” entries are embedded throughout each table page of the QODBC schema documentation. To view all joins comprehensively:

1. Visit https://doc.qodbc.com/qodbc/usa/

2. Select “Table List (USA)” under “Data Layouts”.

3. Each table entry includes “Relations / Jumpins / Detail”, describing its join paths and matching foreign keys.

For further precision, you can programmatically list joinable tables using QODBC’s internal stored procedure:

Running sp_columns on any table (for example, sp_columns InvoiceLine) shows which columns are keys that link to other tables — essentially revealing all possible join relationships.

I am getting the following error trying to insert a record in Invoice:

[QODBC] Not supported - At least one Line record is required. Please insert Child/Detail record(s) before inserting Parent/Header record. (#10074)

Solution:

How to Fix the Error
To resolve this issue, you must change the order of your data insertion or SQL statements to ensure the required detail exists before the header.

Insert the Detail Records First: Before you attempt to insert data into the Parent/Header table (e.g., Invoice), you must successfully insert at least one corresponding record into the Child/Detail/Line table (e.g., InvoiceLine).

INSERT INTO InvoiceLine (InvoiceLineItemRefListID, InvoiceLineDesc, InvoiceLineRate, InvoiceLineAmount, InvoiceLineSalesTaxCodeRefListID, FQSaveToCache) VALUES ( '320000-1071525597', 'POWERTRAK-2000', 200.00000, 200.00, '20000-999022286',1)

INSERT INTO InvoiceLine (InvoiceLineDesc, FQSaveToCache) VALUES ('POWERTRAK-3000', 1)

INSERT INTO InvoiceLine (InvoiceLineDesc, FQSaveToCache) VALUES ('POWERTRAK-4000', 0)

Insert the header record: 

INSERT INTO Invoice (CustomerRefListID, RefNumber, FQSaveToCache) VALUES ('670000-1071517519', '71099',0)

Insert the Header Record Last: Once the detail record(s) are in place, you can then insert the Parent/Header record, completing the transaction.

MS Access:

If you are using MS Access application, the connection string or the connection object is getting closed after you insert the Invoice Line and before you can insert the Invoice (Header) record.
This could be because your linked tables have different connection strings. You can delete the linked table and re-add the linked tables.

If you are using ADO/DOA objects, please ensure you do not close the connection between the insert of InvoiceLine and the Invoice table.

Problem Description:

Since we’re dealing with a lot of sensitive data, is QODBC SOC 2 compliant for the IRS?

Solution:

A common concern when working with sensitive financial data is whether the software in use complies with recognized security standards such as SOC 2 (often referenced in the context of IRS requirements). Customers often ask if the QODBC Driver is SOC 2 compliant.

This concern arises from the assumption that QODBC transmits or stores QuickBooks company file data outside the local environment. However, this is not the case.

• The QODBC Driver does not send QuickBooks company file data to any QODBC server.

• All processing occurs locally on the user’s computer where QuickBooks is installed.

• The optimizer file, which improves query performance, is stored only in the local directory. Furthermore, this file is encrypted, ensuring that sensitive data cannot be accessed in plain text.

Therefore, the typical risks associated with hosted or cloud-based solutions—such as third-party storage, transmission, or centralized processing - do not apply to QODBC.

SOX Compliance

The Sarbanes-Oxley Act (SOX) is designed to regulate financial practices and corporate governance for publicly traded companies. Since QODBC is not operated by a publicly traded company, SOX compliance is not mandatory.

Reference: SOX Compliance Overview

SOC 2 Compliance

SOC 2 compliance focuses on service providers that store, process, or manage customer data. It evaluates how such providers handle data security, availability, processing integrity, confidentiality, and privacy.

In the case of QODBC:

• No customer data is transmitted or stored on QODBC servers.

• All data processing is performed locally on the end user’s environment.

• The QODBC team does not access, manage, or retain QuickBooks company data in any form.

Because QODBC does not operate as a hosted or managed data-processing service, SOC 2 compliance does not apply to its operations.
Reference: SOC 2 Compliance Explained 

QRemote

Please use an encrypted mode of data exchange when using QuickBooks Data remotely.

Please refer to Important Notice About Data Security - QRemote Security, Best Practices, and Recommendations.

Download Sample

Sample Code for using QODBC DSN:

# Array of ListIDs to be updated

$listIDs = @(
"20",
"21",
"22"
)

# Define the DSN name
#$dsnName = "QuickBooks Data"
#$dsnName = "QuickBooks Online Data"

# Add your DSN name here
$dsnName = "Your DSN Name"

Write-Output "Connecting to $dsnName"

# Build connection string
$connStr = "DSN=$dsnName;"

# Create a new ODBC connection
$conn = New-Object System.Data.Odbc.OdbcConnection
$conn.ConnectionString = $connStr

try {
# Open the connection
$conn.Open()
Write-Output "Connected to DSN: $dsnName"

Write-Output "Updating records."
foreach ($listID in $listIDs) {
#Prepare the SQL statement
# Either use ifnull or use the 2nd SQL statement
$sql = @"
UPDATE Account SET Description = {fn IFNULL(Description, '')} + '.' WHERE ListID = '$listID'
"@

# Prepare the SQL statement
$sql = @"
UPDATE Account SET Description = Description + '.' WHERE ListID = '$listID'
"@

Write-Output "SQL statement: $sql"
# Create command
$cmd = $conn.CreateCommand()
$cmd.CommandText = $sql

try {
# Execute the update
$rowsAffected = $cmd.ExecuteNonQuery()
Write-Output "Updated ListID: $listID ($rowsAffected rows affected)"
} catch {
Write-Error "Error updating ListID: $listID - $_"
}
}
}
catch {
Write-Error "Could not connect to ODBC DSN: $dsnName - $_"
}
finally {
# Close the connection
if ($conn.State -eq 'Open') {
$conn.Close()
Write-Output "Connection closed."
}
}

Script execution & Result:

For 32-Bit Driver

Open Windows PowerShell (x86) from the Start menu:

For 64-Bit Driver

Open Windows PowerShell (x64) from the Start menu:

or

Open Windows PowerShell from the Start menu:

Navigate to your PowerShell script folder:

Run your PowerShell script:

Result:

Export the QODBC Online connection key from your computer

Click here for the detailed steps.

Deactivate QODBC Online from your computer

Click here for the detailed steps.

Once you have deactivated QODBC Online from one computer, you can switch to another or a new computer and activate the same CDKEY.

Activate QODBC Online on your new computer

Click here for the detailed steps.

Import the QODBC Online connection key from your computer

Click here for the detailed steps.

QODBC is licensed to each computer. When you purchase a single-user license, you are authorized to use the product on one computer only. If you need to run two computers, you need to purchase another copy.  For contact information, click here.

Keywords
How do I move the license from one server to another?

Swapping the QODBC driver to another machine

Also refer to: QODBC Licensing Information.

The types of licenses needed vary based on your requirements and your environment setup.

Please refer to the detailed information on QODBC Licensing below.

1) Web Server applications accessing QuickBooks remotely with client browsers:

Machine A - QuickBooks, QODBC, QRemote Server, and QuickBooks company file
Machine B - QRemote Client, Web Server, and Web Browsers
Machine C, D, E – Web Browsers

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C, D, E – No QODBC / QRemote License

2) Web Server applications accessing QuickBooks remotely with client applications – QuickBooks company file on a different machine:

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server
Machine B - QRemote Client, Web Server, and Web Browsers
Machine C – QuickBooks company file
Machine D, E, F – Web Browsers

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License
Machine D, E, F – No QODBC / QRemote License

Keywords: QRemote Configuration, QRemote License information, how does Citrix work diagram 

Also refer to: QODBC Licensing Information

The types of licenses needed vary based on your requirements and your environment setup.

Please refer to the detailed information on QODBC Licensing below.

1) Power BI Gateway application accessing QuickBooks remotely:

Machine A - QuickBooks, QODBC, QRemote Server, and QuickBooks company file
Machine B - QRemote Client, Power BI Gateway

License
Machine A – QODBC Server Edition License
Machine B – QRemote License

2) Power BI Gateway application accessing QuickBooks remotely – QuickBooks company file on a different machine. Power BI Gateway application accessing QuickBooks remotely – QuickBooks company file on a different machine.:

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server
Machine B - QRemote Client, Power BI Gateway
Machine C – QuickBooks company file

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License

3) Multiple Power BI Gateway applications accessing QuickBooks remotely:

Machine A - QuickBooks, QODBC, QRemote Server, and QuickBooks company file
Machine B - QRemote Client, Power BI Gateway
Machine C - QRemote Client, Power BI Gateway

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – QRemote License

4) Multiple Power BI Gateway applications accessing QuickBooks remotely – QuickBooks company file on a different machine.:

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server
Machine B - QRemote Client, Power BI Gateway
Machine C – QuickBooks company file
Machine D - QRemote Client, Power BI Gateway

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License
Machine D – QRemote License

5) Multiple Power BI Gateway applications accessing QuickBooks remotely.:

Machine A - QuickBooks, QODBC, QRemote Server, Power BI Gateway, and QuickBooks company file
Machine B - QRemote Client, Power BI Gateway
Machine C - QuickBooks, QODBC, QRemote Server, Power BI Gateway

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – QODBC Server Edition License

6) Multiple Power BI Gateway applications accessing QuickBooks remotely – QuickBooks company file on a different machine.

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server, Power BI Gateway
Machine B - QRemote Client, Power BI Gateway
Machine C – QuickBooks company file
Machine D - QuickBooks, QODBC, QRemote Server, Power BI Gateway

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License
Machine D – QODBC Server Edition License

Keywords: Power BI, Remote Access, QRemote Configuration, QRemote License information

Also refer to: QODBC Licensing Information

The types of licenses needed vary based on your requirements and your environment setup.

Please see the following details for information on QODBC and QRemote licensing while using QuickBooks remotely.

1) SQL Server or service-based applications accessing QuickBooks remotely:

Machine A - QuickBooks, QODBC, QRemote Server, and QuickBooks company file
Machine B - QRemote Client, SQL Server, and SQL Server Management Studio

License
Machine A – QODBC Server Edition License
Machine B – QRemote License

2) SQL Server or service-based applications accessing QuickBooks remotely – QuickBooks company file on a different machine:

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server
Machine B - QRemote Client, SQL Server, and SQL Server Management Studio
Machine C – QuickBooks company file

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License

3) SQL Server or service-based applications accessing QuickBooks remotely with client applications:

Machine A - QuickBooks, QODBC, QRemote Server, and QuickBooks company file
Machine B - QRemote Client, SQL Server, and SQL Server Management Studio
Machine C, D, E – SQL Server Management Studio

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C, D, E – No QODBC / QRemote License

4) SQL Server or service-based applications accessing QuickBooks remotely with client applications – QuickBooks company file on a different machine:

Note: Accessing a QuickBooks company file from a different computer or shared drive can impact the performance of both QuickBooks and QODBC. Thus, we do not recommend such an environment setup. To achieve the best performance, it is advisable to run QODBC, the QuickBooks application, and the QuickBooks company file on the same computer.

Machine A - QuickBooks, QODBC, QRemote Server
Machine B - QRemote Client, SQL Server, and SQL Server Management Studio
Machine C – QuickBooks company file
Machine D, E, F – SQL Server Management Studio

License
Machine A – QODBC Server Edition License
Machine B – QRemote License
Machine C – No QODBC / QRemote License
Machine D, E, F – No QODBC / QRemote License

Keywords: QRemote Configuration, QRemote License information, how does Citrix work diagram 

Problem Description:

I have installed QODBC Online build 358.

I can connect to the QuickBooks Online company file using QODBC Online 32-bit DSN.

I have created a new QODBC Online DSN 64-Bit.

When I am trying to connect to the QuickBooks Online company file using QODBC Online 64-Bit DSN, on the browser, it says connected, but the DSN still shows "Connect to QuickBooks," and it does not connect.

Sometimes the DSN window disappears.

Solution:

Updates (2025-05-30):

We are currently working on fixing the issue, and we will soon release a new build.

The issue is limited to when using the new QODBC Online 64-bit DSN.

If you are using a single QuickBooks Online company file, you can use "QuickBooks Data Online" from a 32-bit system.

Once you connect to your QuickBooks Online company file using a 32-bit "QuickBooks Online Data" DSN, this will automatically update your "QuickBooks Online Data" 64-bit.

You should be able to use "QuickBooks Online Data" 64-bit.

If you wish to create your own QODBC Online DNS, you can use one of the following workarounds.

Workaround 1:

Use QODBC Online 32-bit DSN, connect to the QuickBooks Online company file.

Once connected, export the connection key from the 32-bit.

Problem Description:

I am using Microsoft Excel 365 and trying to import data using the Microsoft Query option. However, I cannot find Microsoft Query (Legacy) under the Get Data tab.
Why is Microsoft Query (Legacy) missing in Excel 365, and how can I enable it?

Solution:

In recent versions of Microsoft Excel (including Excel 365), the Microsoft Query (Legacy) feature is hidden by default from the Get Data tab. This tool is commonly used to import data from external sources via ODBC connections. If you're using QODBC or any ODBC-based system like QuickBooks, enabling this option is necessary.

Note: We recommend using the 64-bit version of Microsoft Excel for better performance and compatibility when working with large datasets.

Prerequisites:

Microsoft Excel 2016 or later (including Excel 365)
Administrative access to change Excel options.

As shown in the above image, the Microsoft Query option does not appear under the Get Data tab by default.

Step-by-Step Instructions to enable Microsoft Query:

Step 1: Enable Legacy Data Import Wizards.

• Open Microsoft Excel.

• Click on the File tab.

• Click on Options at the bottom-left corner.

• In the Excel Options window, select the Data category from the left-hand panel.

• Scroll down to the Legacy Data Import Wizards section.

• Check the box labeled "From Microsoft Query (Legacy)".

•  Click OK to apply changes.

•  Close and restart Excel for the changes to take effect.

Step 2: Access Microsoft Query (Legacy)

After restarting Excel:

• Go to the Data tab.

• Click Get Data > Legacy Wizards > From Microsoft Query (Legacy).

By following the steps above, you can restore and use the Microsoft Query (Legacy) wizard in Excel 365, allowing seamless data import via QODBC from external applications such as QuickBooks.

Tags: "Microsoft Query" is not a data option. Microsoft Query is missing. How to enable Microsoft Query and show Microsoft Query.

Problem Description:

I would like to use the new QuickBooks integrator module from Bookkeeper to allow me to import data directly into Bookkeeper.

Solution:

1. Create a New Company in Bookkeeper

• Launch Bookkeeper and create a new company (this will be the target for the QuickBooks data).

• Choose the standard setup.

• Enter basic company info (it will be overwritten during import).

• Set:

  • Accounting method (irrelevant, will be replaced).

  • Next fiscal year-end.

  • Advanced Payroll (ensure this is selected).

• Set a password.

• Select “Import from QuickBooks” and click Import.

 Please ensure you have downloaded and installed the "QuickBooks Integrator tool."

2. Prepare the Bookkeeper Database for Integration

• Click “Prepare Integration” in Bookkeeper.

• Ensure you have taken a backup of your Bookkeeper database.

• The bookkeeper will copy the integration tool to the Integration folder and will shut down the Bookkeeper application.

• This will copy the database to a staging area for the integrator module.

3. Open QuickBooks

• Start QuickBooks and log in to the QuickBooks company file as QuickBooks user "Admin".

• Important: Do not run QuickBooks as an administrator.

   

4. Open the QuickBooks Integrator Module

• Double-click on the QuickBooks Integration tool from the Desktop

• Important: Do not run QuickBooks as an administrator.

• Click the "Connect" button.

• When prompted by QuickBooks, allow access and confirm the connection.

• You should see the QuickBooks company name.

5. Connect to Bookkeeper

• Click “Connect” in the Integrator to connect to the Bookkeeper company you created.

• Select the correct company from the dropdown list if needed.

• Select the Bookkeeper company from the list.

6. Configure Import Options

• Optionally select a start date to limit historical data.

• By default, company info, bank accounts, and the chart of accounts are imported.

• Choose whether to import:

  • Transactions

  • Lists (customers, vendors, etc.)

• Click “Start” to begin the import.

   

7. Monitor the Import Process

• The integrator will show status messages and record counts.

• Large datasets may take hours, depending on size.

• Let the process complete fully.

8. Finish Integration in Bookkeeper

• After completion, close the integrator module.

• Launch Bookkeeper from the desktop. Right-click on the Bookkeeper shortcut icon and click Run as Administrator.

• Go to File > Import > Complete Integration.

• This copies the staged database back into Bookkeeper.

• This copies the staged database back into Bookkeeper.

• The Bookkeeper application will restart.

9. View Imported QuickBooks Data

• Reopen Bookkeeper (Run as Administrator).

• Log in with your set password.

• You’ll now see all your QuickBooks data:

  
  

  • Bank accounts

  • Customers

  • Vendors

  • Transactions

 Important Tips

• Don’t run QuickBooks or the Integrator as Administrator.

• Run Bookkeeper as Administrator only during the final import step.

• Be selective with data to import to save time and avoid performance issues.

Problem Description:

I want to get a copy of the invoice for my QODBC subscription.
 

Solution:

Please visit the following link: https://flexquarters.onfastspring.com/account.

Input the email address associated with your license.

Check your email inbox, and you should receive an email with the subject:

<Your Fullname>, here is a link to manage your orders

From: FastSpring Checkout <mailer@fastspring.com>

Click the link received to manage your account.

The link (URL) should look like https://flexquarters.onfastspring.com/account/somerandomtext

Click Get Invoice

Tags: QuickBooks Desktop, QBD, Desktop Subscription, QODBC Desktop, manage subscription

Problem Description:

QODBC stopped working this morning, and I got a message that / License verification is required.  I opened License Sync and hit the "Sync Now" button. It seems like something might be happening, but I get no message of any sort popping up, and QODBC still has the message that license sync needs to be run. How can I resolve this?

Problem Description:

Where/How do I use License Sync to verify my QODBC license?

Solution:

Solution applicable to "QODBC for QuickBooks Desktop":

Problem Description:

We have an issue with QuickBooks Desktop 24. I have downloaded the latest driver, and I have the latest QuickBooks. 

The connection continuously fails and gives us a security message about wanting to enable it in QuickBooks for that specific computer and user, and it was working with the older version of QuickBooks 23 and the older driver, and something has changed. We are uncertain as to what needs to be changed.

Solution:

Start QuickBooks and log in to the QuickBooks company file as QuickBooks user "Admin".
Connect to QuickBooks Data using the QODBC 32-Bit Test Tool.
Switch to QuickBooks and check if there is any prompt. Please accept the certificate/integrated application permissions (if any).
Disconnect
Connect to QuickBooks Data using your application.

>> The connection continuously fails and gives us a security message about wanting to enable it in QuickBooks

Intuit has recently added a new security feature - https://quickbooks.intuit.com/learn-support/image/serverpage/image-id/84123iE5E2A8E37E4C0D0E/image-size/large
When prompted, please input your Intuit account information to suppress the pop-up.

In your QuickBooks Desktop, go to the Company menu.
Next, select the My Company option.
From there, you can log in to your account.
You can save your Primary Admin credentials, and you will be asked to log in every 180 days.

Please also refer to the following articles.
https://quickbooks.intuit.com/learn-support/en-us/account-management/has-anyone-been-able-to-get-rid-of-popups-and-login-requirements/00/1136260
https://quickbooks.intuit.com/learn-support/en-us/other-questions/sign-in-required-pop-up/00/1479029

If you are still having the issue, please attach the files listed below to find the issue.

Screenshot of QODBC Setup Screen -- > About (Start>>All Programs>> QODBC Driver for QuickBooks>> QODBC Setup Screen >> About Tab)
Screenshot of the problem you are facing. (Please send it as an attachment) - Full Screen
Log Files from
QODBC Setup Screen -- > Messages -- > Review QODBC Messages (Please send it as an attachment)
QODBC Setup Screen -- > Messages -- > Review SDK Messages (Please send it as an attachment)

Problem Description:

How do I fix the QODBC license file stored in VirtualStore

Solution:

Please remove the folder "QODBC Driver for QuickBooks" from the path below
C:\Users\YourName\AppData\Local\VirtualStore\ProgramData\QODBC Driver for QuickBooks

Please remove the folder "QODBC Driver for QuickBooks Online" from the path below.

C:\Users\YourName\AppData\Local\VirtualStore\ProgramData\QODBC Driver for QuickBooks Online

Problem Description:

When I connect to QODBC, I am prompted to free disk space.

Solution:

Please ensure you have 1 GB of free space in your primary drive where your Windows Profile / Roaming Profile or QODBC Optimizer folder is saved.

Ideally, it is the "C" Drive

Location

%appdata%\QODBC Driver for QuickBooks

Example

C:\Users\YourWindowsUserName\AppData\Roaming\QODBC Driver for QuickBooks

On your C Drive, you should have 1 GV free space available.

Alternatively, you can turn off the optimizer from the QODBC 32-Bit Setup Screen.

Problem Description:

How to resolve duplicate default DSN. 

Solution:

Configure 64-Bit QODBC Online Driver and switch to "User DSN".

Please delete the DSNs with the following names.

"QuickBooks Data"

"QuickBooks Online Data"

"QuickBooks POS Data"

Close the ODBC Data Source Manager

Configure the 32-bit QODBC Online Driver and switch to "User DSN".

Please delete the DSNs with the following names.

"QuickBooks Data"

"QuickBooks Online Data"

"QuickBooks POS Data"

Close the ODBC Data Source Manager 

Problem Description:

What should be the Default Windows User Access Control (UAC)?

Solution:

The QODBC Driver for QuickBooks runs differently under Microsoft Vista/Windows 7 than other versions of Windows because of its new, strict security settings.

UAC (User Account Control): This new technology in Windows Vista has been used to improve system security. It asks all users for permission to run programs and tasks under a standard account module. It can prevent the installation of programs without authentication and contain an inappropriate system setup change from a regular user.

Please open the Windows Start menu and type or search for "Windows User Access Control" (UAC)

Please set the default value of Windows User Access Control (UAC) to the following (as per your Windows Operating system edition).

Windows 10 and Windows 11

Windows 7

Start -> Control Panel -> User Account -> Open "User Account Control" (UAC) -> Change User Account Controls

Please Also Refer: Connecting QODBC Driver to QuickBooks for the First Time (Video)

Problem Description:

I want to cancel my QODBC Driver for QuickBooks Desktop monthly subscription.

How do I cancel the subscription to the QODBC Driver for QuickBooks Desktop?

Solution:

Start QuickBooks and log in to the QuickBooks company file as QuickBooks user "Admin".

Connect to QuickBooks Data using the QODBC 32-bit Test Tool.

Execute the following SQL statement.

sp_optimizefullsync TableName

example

sp_optimizefullsync Customer
or

sp_optimizefullsync Vendor

or

sp_optimizefullsync Invoice

Tags: QuickBooks Desktop, QBD, Desktop Subscription QODBC Desktop, Cancel subscription

Start QuickBooks and log in to the QuickBooks company file as QuickBooks user "Admin".

Connect to QuickBooks Data using the QODBC 32-bit Test Tool.

Execute the following SQL statement.

sp_optimizefullsync TableName

example

sp_optimizefullsync Customer

or

sp_optimizefullsync Vendor

or

sp_optimizefullsync Invoice

Problem Description:

I want to cancel my QODBC Driver for QuickBooks Desktop monthly subscription.

How do I cancel the subscription to the QODBC Driver for QuickBooks Desktop?

I received an email saying a subscription was going to be renewed. I need to cancel this subscription.

Solution:

Latest Method:

Please visit the following link: https://flexquarters.onfastspring.com/account.

Input the email address associated with your license.

Check your email inbox, and you should receive an email with the subject:

<Your Fullname>, here is a link to manage your orders

From: FastSpring Checkout <mailer@fastspring.com>

Click the link received to manage your account.

The link (URL) should look like https://flexquarters.onfastspring.com/account/somerandomtext.

Latest Method:

You can manage the subscription of the QODBC Driver for QuickBooks Desktop using the link you received in your renewal email.

On your monthly subscription renewal receipt, you will see the following, as in this example:

Order ID: FLE1XXXXX-1XXX-6XXXXB
1 QODBC Desktop Driver for QuickBooks Desktop USA
https://sites.fastspring.com/flexquarters/order/s/ (your order number). Click on this link on YOUR receipt, and you can cancel the subscription.

Example
https://sites.fastspring.com/flexquarters/order/s/FLE111111-1111-111111

Please visit that link & click on Cancel Subscription to cancel your QODBC Desktop subscription:

Tags: QuickBooks Desktop, QBD, Desktop Subscription QODBC Desktop, Cancel subscription, Manage my Account

Problem Description:

I want to modify a few configurations of the QRemote Server.

When I apply the changes, I get the following message.

Unable to save the changes to the configuration file.

For more information, please visit

qodbc.com/links/QRemoteFailToSaveConfig

Solution:

Click the Windows Start button and type "Run".

Type "C:\ProgramData" in the Run Window.

Navigate to the QODBC folder, depending on the application you are using.

"QODBC Driver for QuickBooks" or "QODBC Driver for QuickBooks Online" or "QODBC Driver for QuickBooks POS"

Delete the file "QRemoteServerConfig.ini" from the location listed below:

C:\ProgramData\QODBC Driver for QuickBooks

Select "QRemoteServerConfig.ini" and click the delete icon.

After deleting the file "QRemoteServerConfig.ini," exit QRemote Server.

QRemote Server --> File --> Exit.

Stored Procedures Command List

Applicable to [QODBC-Desktop], [QODBC-Online], [QODBC-POS], [QXL- Desktop] & [QXL- Online] 

Stored Procedures

SP_COLUMNS table name

Instruction: Returns a recordset of the columns in the specified table.

Example: sp_columns Customer

Returns:

SP_FQSAVETOCACHEROLLBACK on|off

Instruction: Sets or clears whether the cache is backed up or reset if an error occurs when doing multiple inserts using the FQSaveToCache flag field. The off mode can help with performance if the rollback is not needed. The default is on.

Example: sp_fqsavetocacherollback off

Returns: This is an execute the command and does not return a recordset.

SP_LASTINSERTID

Instruction: Returns a recordset with one row (or multiple rows if done after a sp_batchupdate command) and two columns containing the last ListID or last TxnID from the last insert done and its error status on the current connection. The value is obtained from the return value of the previous insert (or inserts if done inside a sp_batchstart/sp_batchupdate block) performed on the same connection for that table.

Example: sp_lastinsertid Customer

Returns:

SP_LASTINSERTIDRETURN  on|off

Instruction: Sets or clears whether the last insert ID is returned.

Example: sp_lastinsertidreturn off

Returns: This is an execute the command and does not return a recordset.

SP_OPTIMIZEFULLSYNC  tablename|ALL

Instruction: This command will reload the specified table from scratch. It helps ensure that the optimizer perfectly syncs with the QuickBooks company file. The ALL option will do all tables.

Example: sp_optimizefullsync Customer

Returns: This is an execute the command and does not return a recordset.

SP_OPTIMIZEUPDATESYNC tablename|ALL

Instruction: This command will synchronize the specified table with the QuickBooks data file using changed and deleted data. It helps ensure that the optimizer is up to date with the QuickBooks company file. The ALL option will do all tables.

Example: sp_optimizeupdatesync Customer

Returns: This is an execute the command and does not return a recordset.

SP_PRIMARYKEYStablename

Instruction: Returns a recordset of the primary key segments in the specified table.

Example: sp_primarykeys Customer

Returns:

SP_QBFILENAME

Instruction: This command returns the full path to the open QuickBooks company file. It returns a one-column, one-row record set.

Example: sp_qbfilename

Returns:

*Note: sp_report and other report commands are unavailable for QODBC POS. QuickBooks POS SDK does not support reports, and thus it is not available in QODBC POS.

SP_REPORTtablename [show]

Instruction: Similar to the SQL Keyword SELECT. Used to run built-in QuickBooks reports. See http://www.qodbc.com/data, make your country selection, then select the REPORTS link.

Example: sp_report ARAgingSummary show Current_Title, Amount_Title, Text, Label, Current, Amount parameters DateMacro = ‘Today', AgingAsOf = ‘Today'

Returns:

SP_REPORTS

Instruction: Returns a recordset of the information of all reports.

Example: sp_reports  

Returns:

SP_SPECIALCOLUMNS  tablename [ ROWVER ]|[ BEST_ROWID ]

Instruction: Returns a recordset of the special columns. RowVer describes which column holds the row ID, and Best_RowID describes the column that is the row identifier. Best_RowID is the default if neither is specified.

Example: sp_specialcolumns Customer Best_RowID

Returns:

Example2: sp_specialcolumns Customer RowVer  

Returns:  

SP_TABLES  table name

Instruction: Returns a recordset with the list of tables available from the ODBC Driver.

Example: sp_tables

Returns:

SP_CATEGORIES

Instruction: Returns a recordset with the list of categories for all the tables.

Example: sp_categories

Returns:

SP_CATEGORYTABLES

Instruction: Returns a recordset with the list of all the tables and the categories they belong to.

Example: sp_categorytables

Returns:

SP_CATEGORYREPORTS

Instruction: Returns a recordset with the list of all the reports and the categories they belong to.

Example: sp_categoryreports

Returns:

SP_FOREIGNKEYS  table name table name

Instruction: Returns a recordset of the detailed relationship information of two tables.

Example: sp_foreignkeys Customer Invoice

Returns:

SP_PARAMETERS

Instruction: Returns a recordset with the list of the detailed information of parameters of each report.

Example: sp_parameters

Returns:

SP_STATISTICS  tablename

Instruction: Returns a recordset with the list of all the indexes and a list of statistical information of the specified table or indexed view.

Example: sp_statistics Customer

Returns:

Keywords: last insert id

Function List

Applicable to [QODBC-Desktop], [QODBC-Online], [QODBC-POS], [QXL- Desktop] & [QXL- Online] 

Functions

     This is a list of all of the SQL functions supported by the QODBC Driver and their associated syntax.

QODBC String Functions

ASCII ( string_exp )

Instruction: Returns the ASCII code value of the leftmost character of string_exp as an integer.

Example: SELECT {fn ASCII("Name")} AS "ASCII", "Name" FROM Customer

Returns:

CHAR ( code )

Instruction: Returns the character with the ASCII code value specified by the code. The code value should be between 0 and 255; otherwise, the return value is data source-dependent.

Example: SELECT {fn CHAR(65)} +  {fn CHAR(66)} AS "APlusB", "Name" FROM Customer

Returns:

CONCAT ( string_exp1, string_exp2 )

Instruction: Returns a character string that results from concatenating string_exp2 to string_exp1. A NULL value will be returned if the column represented by string_exp1 or string_exp2 contains a NULL value.

Example: SELECT {fn CONCAT("BillAddressState", "BillAddressPostalCode")} AS "STZip", "Name" FROM Customer

Returns:

DIFFERENCE ( string_exp1, string_exp2 )

Instruction: Returns an integer value that indicates the difference between the values returned by the SOUNDEX function for string_exp1 and string_exp2.

Example: SELECT {fn DIFFERENCE("Name", 'Abercrombie, Kristy')} AS "Difference", "Name" FROM Customer

Returns:

INSERT ( string_exp1, start, length, string_exp2 )

Instruction: Returns a character string where length characters have been deleted from the string_exp1 beginning at the start and where string_exp2 has been inserted into string_exp1, beginning at the start.

Example: SELECT {fn INSERT("Name", 3, 2, '*Inserted*')} AS "Inserted", "Name" FROM Customer

Returns:

LCASE ( string_exp )

Instruction: Converts all uppercase characters in string_exp to lowercase.

Example: SELECT {fn LCASE("Name")} AS "LCase", "Name" FROM Customer

Returns:

UCASE ( string_exp )

Instruction: Converts all lowercase characters in string_exp to uppercase.

Example: SELECT {fn UCASE("Name")} AS "UCase", "Name" FROM Customer

Returns:

LEFT ( string_exp, count )

Instruction: Returns the leftmost count of characters of string_exp.

Example: SELECT {fn LEFT("Name", 5)} AS "Left5", "Name" FROM Customer

Returns:

RIGHT ( string_exp, count )

Instruction: Returns the rightmost count of characters of string_exp.

Example: SELECT {fn RIGHT(“Name”, 5)} AS "Right5", "Name" FROM Customer

Returns:

LENGTH ( string_exp )

Instruction: Returns the number of characters in string_exp, excluding trailing blanks and the string termination character.

Example: SELECT {fn LENGTH("Name")} AS "Length", "Name" FROM Customer

Returns:

BIT_LENGTH ( string_exp )

Instruction: Returns the bit length of string_exp, excluding trailing blanks and the string termination character.

Example: SELECT {fn BIT_LENGTH("Name")} AS "BitLength", "Name" FROM Customer

Returns:

CHAR_LENGTH ( string_exp )

Instruction: Returns the number of chars in string_exp, excluding trailing blanks and the string termination character.

Example: SELECT {fn CHAR_LENGTH("Name")} AS "CharLength", "Name" FROM Customer

Returns:

CHARACTER_LENGTH ( string_exp )

Instruction: Returns the number of characters in string_exp, excluding trailing blanks and the string termination character. (Almost the same as the LENGTH function)

Example: SELECT {fn CHARACTER_LENGTH("Name")} AS "CharacterLength", "Name" FROM Customer

Returns:

OCTET_LENGTH ( string_exp )

Instruction: Returns the octet length of string_exp, excluding trailing blanks and the string termination character. (Almost the same as the LENGTH function)

Example: SELECT {fn OCTET_LENGTH("Name")} AS "OctetLength", "Name" FROM Customer

Returns:

LOCATE ( string_exp1, string_exp2[, start] )

Instruction: Returns the starting position of the first occurrence of string_exp1 within string_exp2. The search for the first occurrence of string_exp1 begins with the first position in string_exp2 unless the optional argument is specified. If the start is set, the search begins with the character position indicated by the value birth. The first character position in string_exp2 is indicated by the value 1. If string_exp1 is not found within string_exp2, the value 0 is returned.

Example: SELECT {fn LOCATE('a', "Name", 2)} AS "LocationOfA", "Name" FROM Customer

Returns:

LTRIM ( string_exp )

Instruction: Returns the characters of string_exp, with leading blanks removed.

Example: SELECT {fn LTRIM("Name")} AS "LTrim", "Name" FROM Customer

Returns:

RTRIM ( string_exp )

Instruction: Returns the characters of string_exp, with trailing blanks removed.

Example: SELECT {fn RTRIM("Name")} AS "RTrim", "Name" FROM Customer

Returns:

REPEAT ( string_exp1, repeat times )

Instruction: Returns the characters of string_exp1, repeating it repeat times.

Example: SELECT {fn REPEAT("Name",2)} as "Repeat2","Name" FROM Customer

Returns:

POSITION ( string_exp1, string_exp2 )

Instruction: Returns an integer value that shows the position where string_exp1 first begins in string_exp2 (including spaces)

Example: SELECT {fn POSITION('a' IN "Name")} As "PositionOfA", "Name" FROM Customer

Returns:

REPLACE ( string_exp1, string_exp2,string_exp3 )

Instruction: Returns the characters of string_exp3, which takes the place of string_exp2 value in column string_exp1.

Example: SELECT {fn REPLACE("NAME",'330 Main St','abc')} AS "Replace","Name" FROM Customer

Returns:

SOUNDEX ( string_exp )

Instruction: Returns a character string representing the sound of the words in string_exp.

Example: SELECT {fn SOUNDEX("Name")} AS "Soundex", "Name" FROM Customer

Returns:

SPACE ( count )

Instruction: Returns a character string consisting of count spaces.

Example: SELECT '[' + {fn SPACE(10)} + ']' AS "TenSpaces", "Name" FROM Customer

Returns:

SUBSTRING ( string_exp, start, length )

Instruction: Returns a character string that is derived from string_exp beginning at the character position specified by start for length characters.

Example: SELECT {fn SUBSTRING("Name", 2, 5)} AS "Middle5Characters", "Name" FROM Customer

Returns:

QODBC Numeric Functions

ABS ( numeric_exp|float_exp|integer_exp )

Instruction: Returns the absolute value of numeric_exp.

Example: SELECT "Name", {fn ABS(Balance)} AS "ABSBalance", "Balance" FROM Customer

Returns:

ACOS ( float_exp )

Instruction: Returns the arccosine of float_exp as an angle, expressed in radians.

Example: SELECT {fn ACOS({fn CONVERT(0, SQL_FLOAT)})} AS "ACOSValue", CompanyName AS "CompanyName" FROM Company

Returns:

ASIN ( float_exp )

Instruction: Returns the arcsine of float_exp as an angle, expressed in radians.

Example: SELECT {fn ASIN({fn CONVERT(0, SQL_FLOAT)})} AS "ASINValue", CompanyName AS "CompanyName" FROM Company

Returns:

ATAN ( float_exp )

Instruction: Returns the arctangent of float_exp as an angle, expressed in radians.

Example: SELECT {fn ATAN({fn CONVERT(1, SQL_FLOAT)})} AS "ATANValue", CompanyName AS “CompanyName” FROM Company

Returns:

ATAN2 ( float_exp1, float_exp2 )

Instruction: Returns the arctangent of the x and y coordinates specified by float_exp1 and float_exp2, respectively, as an angle, expressed in radians.

Example: SELECT {fn ATAN2({fn CONVERT(1, SQL_FLOAT)}, {fn CONVERT(2, SQL_FLOAT)})} AS "ATAN2Value", CompanyName AS “CompanyName” FROM Company

Returns:

COS ( float_exp )

Instruction: Returns the cosine of float_exp, where float_exp is an angle expressed in radians.

Example: SELECT {fn COS({fn CONVERT(1, SQL_FLOAT)})} AS "COSValue", CompanyName AS “CompanyName” FROM Company

Returns:

COT ( float_exp )

Instruction: Returns the cotangent of float_exp, where float_exp is an angle expressed in radians.

Example: SELECT {fn COT({fn CONVERT(1, SQL_FLOAT)})} AS "COTValue", CompanyName AS “CompanyName” FROM Company

Returns:

CEILING ( numeric_exp|float_exp|integer_exp )

Instruction: Returns the smallest integer greater than or equal to numeric_exp.

Example: SELECT "Name", {fn CEILING("Balance")} AS "CeilingBalance", "Balance" FROM Customer

Returns:

DEGREES ( numeric_exp|float_exp|integer_exp )

Instruction: Returns the number of degrees converted from numeric_exp radians.

Example: SELECT {fn DEGREES(1)} AS "DegreesReturned", CompanyName AS “CompanyName” FROM Company

Returns:

EXP ( float_exp )

Instruction: Returns the exponential value of float_exp.

Example: SELECT {fn EXP({fn CONVERT(1, SQL_FLOAT)})} AS "ExpReturned", CompanyName AS “CompanyName” FROM Company

Returns:

FLOOR (numeric_exp|float_exp|integer_exp)

Instruction: Returns the largest integer less than or equal to numeric_exp.

Example: SELECT "Name", {fn FLOOR("Balance")} AS "FloorBalance", "Balance" FROM Customer

Returns:

LOG ( float_exp )

Instruction: Returns the natural logarithm of float_exp.

Example: SELECT {fn LOG({fn CONVERT(25, SQL_FLOAT)})} AS "LogReturned", CompanyName AS “CompanyName” FROM Company

Returns:

LOG10 ( float_exp )

Instruction: Returns the base ten logarithm of float_exp.

Example: SELECT {fn LOG10({fn CONVERT(25, SQL_FLOAT)})} AS "Log10Returned", CompanyName AS “CompanyName” FROM Company

Returns:

MOD ( integer_exp1, integer_exp2 )

Instruction: Returns the remainder (modulus) of integer_exp1 divided by integer_exp2.

Example: SELECT {fn MOD(27, 7)} AS "Mod7Returned", CompanyName AS “CompanyName” FROM Company

Returns:

PI ()

Instruction: Returns the constant value of pi as a floating point value.

Example: SELECT {fn PI()} AS "PI", CompanyName AS “CompanyName” FROM COMPANY

Returns:

POWER ( numeric_exp|float_exp|integer_exp, integer_exp )

Instruction: Returns the value of numeric_exp to the power of integer_exp.

Example: SELECT {fn POWER(4, 3)} AS "PowerValue", CompanyName AS "CompanyName" FROM COMPANY

Returns:

RADIANS ( numeric_exp|float_exp|integer_exp )

Instruction: Returns the number of radians converted from numeric_exp degrees.

Example: SELECT {fn RADIANS(57.29578)} AS "RadiansValue", CompanyName AS “CompanyName” FROM COMPANY

Returns:

RAND ([ integer_exp|float_exp|numeric_exp ])

Instruction: Returns a random floating point value using integer_exp as an optional seed value.

Example: SELECT {fn RAND()} AS "RandValue" FROM COMPANY

Returns:

ROUND ( numeric_exp|float_exp|integer_exp, integer_exp )

Instruction: Returns numeric_exp rounded to integer_exp placed right of the decimal point. If integer_exp is negative, numeric_exp is rounded to | integer_exp | and placed to the left of the decimal point.

Example: SELECT "Name", {fn ROUND(Balance, 1)} AS "RoundBalance", "Balance" FROM Customer

Returns:

SIGN ( numeric_exp|float_exp|integer_exp )

Instruction: Returns an indicator or the sign of numeric_exp. If numeric_exp is less than zero, -1 is returned. If numeric_exp equals zero, 0 is returned. If numeric_exp is more significant than zero, one is returned.

Example: SELECT "Name", {fn SIGN(Balance)} AS "SignOfBalance", "Balance" FROM Customer

Returns:

SIN ( float_exp )

Instruction: Returns the sine of float_exp, where float_exp is an angle expressed in radians.

Example: SELECT {fn SIN({fn CONVERT(1, SQL_FLOAT)})} AS "SINValue", CompanyName AS “CompanyName” FROM Company

Returns:

SQRT ( float_exp )

Instruction: Returns the square root of float_exp.

Example: SELECT {fn SQRT({fn CONVERT(47, SQL_FLOAT)})} AS "SQRTValue", CompanyName AS “CompanyName” FROM Company

Returns:

TAN ( float_exp )

Instruction: Returns the tangent of float_exp, where float_exp is an angle expressed in radians.

Example: SELECT {fn TAN({fn CONVERT(1, SQL_FLOAT)})} AS "TANValue", CompanyName AS “CompanyName” FROM Company

Returns:

TRUNCATE ( numeric_exp|float_exp|numeric_exp, integer_exp )

Instruction: Returns numeric_exp truncated to integer_exp places right of the decimal point. If integer_exp is negative, numeric_exp is truncated to | integer_exp | places to the left of the decimal point.

Example: SELECT "Name", {fn TRUNCATE(Balance, 1)} AS "TruncateBalance", "Balance" FROM Customer

Returns:

QODBC Time and Date Functions

CURDATE ()

Instruction: Returns the current date as a date value.

Example: SELECT {fn CURDATE()} AS "CurDate" FROM Company

Returns:

CURRENT_DATE ()

Instruction: Returns the current date as a date value.

Example: SELECT {fn CURDATE_DATE()} AS "CurrentDate" FROM Company

Returns:

CURTIME()

Instruction: Returns the local time as a time value.

Example: SELECT {fn CURTIME()} AS "CurTime" FROM Company

Returns:

CURRENT_ TIME()

Instruction: Returns the current time as a time value.

Example : SELECT {fn CURRENT_TIME()} AS "CurrentTime" FROM Company

Returns:

CURRENT_ TIMESTAMP()

Instruction: Returns the current date and time as a timestamp value.

Example: SELECT {fn CURRENT_TIMESTAMP()} AS "CurrentTimeStamp" FROM Company

Returns:

DAYNAME ( date_exp )

Instruction: Returns a character string containing the data source-specific name of the day (for example, Sunday through Saturday or Sun. through Sat. for a data source that uses English) for the day portion of date_exp.

Example: SELECT {fn DAYNAME({fn CURDATE()})} AS "CurDayName", CompanyName AS "CompanyName" FROM Company

Returns:

DAYOFMONTH ( date_exp| string_exp|timestamp_exp )

Instruction: Returns the day of the month in date_exp as an integer value in the range of 1-31.

Example: SELECT {fn DAYOFMONTH({fn CURDATE()})} AS "CurDayOfMonth" FROM Company

Returns:

DAYOFWEEK ( date_exp )

Instruction: Returns the day of the week in date_exp as an integer value in the range of 1-7, where one represents Sunday.

Example: SELECT {fn DAYOFWEEK({fn CURDATE()})} AS "CurDayOfWeek" FROM Company

Returns:

DAYOFYEAR ( date_exp )

Instruction: Returns the day of the year in date_exp as an integer value in the range of 1-366.

Example: SELECT {fn DAYOFYEAR({fn CURDATE()})} AS "CurDayOfYear" FROM Company

Returns:

EXTRACT( date_exp|timestamp_exp )

Instruction: Returns the part of date_exp or timestamp_exp.

Example: SELECT {fn EXTRACT(YEAR FROM{fn CURRENT_DATE()})} AS "Year",{fn EXTRACT(MONTH FROM{fn CURRENT_DATE()})} AS "Month",{fn EXTRACT(DAY FROM{fn CURRENT_DATE()})} AS "Day", CompanyName as "CompanyName" FROM Company

Returns:

HOUR ( time_exp| string_exp|timestamp_exp )

Instruction: Returns the hour in time_exp, char_exp, or timestamp_exp as an integer value in the range of 0-23.

Example: SELECT {fn HOUR({fn CURTIME()})} AS "CurHour" FROM Company

Returns:

MINUTE ( time_exp| string_exp|timestamp_exp )

Instruction: Returns the minute in time_exp as an integer value in the range of 0-59.

Example: SELECT {fn MINUTE({fn CURTIME()})} AS "CurMinute" FROM Company

Returns:

MONTH ( date_exp| string_exp|timestamp_exp )

Instruction: Returns the month in date_exp as an integer value in the range of 1-12.

Example: SELECT {fn MONTH({fn CURDATE()})} AS "CurMonth" FROM Company

Returns:

MONTHNAME ( date_exp| string_exp|timestamp_exp )

Instruction: Returns a character string containing the data source-specific name of the month (for example, January through December or Jan. through Dec. for a data source that uses English) for the month portion of date_exp.

Example: SELECT {fn MONTHNAME({fn CURDATE()})} AS "CurMonthName”, CompanyName AS "CompanyName" FROM Company

Returns:

NOW ()

Instruction: Returns the current date and time as a timestamp value.

Example: SELECT {fn NOW()} AS "Now" FROM Company

Returns:

QUARTER ( date_exp| string_exp|timestamp_exp )

Instruction: Returns the quarter in the date_exp as an integer value in the range of 1-4, where 1 represents January 1 through March 31.

Example: SELECT {fn QUARTER({fn CURDATE()})} AS "CurQuarter", CompanyName AS "CompanyName" FROM Company

Returns:

SECOND ( time_exp| string_exp|timestamp_exp )

Instruction: Returns the second in time_exp as an integer value in the range of 0-59.

Example: SELECT {fn SECOND({fn CURTIME()})} AS "CurSecond" FROM Company

Returns:

TIMESTAMPADD ( interval, integer_exp, timestamp_exp )

Instruction: Returns the timestamp calculated by adding integer_exp intervals of type interval to timestamp_exp. Valid values of interval are the following keywords: SQL_TSI_FRAC_SECOND, SQL_TSI_HOUR, SQL_TSI_SECOND, SQL_TSI_DAY, SQL_TSI_MINUTE, SQL_TSI_WEEK, SQL_TSI_MONTH, SQL_TSI_QUARTER, SQL_TSI_YEAR, where fractional seconds are expressed in billionths of a second.

Notes: If timestamp_exp is a time value and interval specifies days, weeks, months, quarters, or years, the date portion of timestamp_exp is set to the current date before calculating the resulting timestamp.

     If timestamp_exp is a date value and interval specifies fractional seconds, seconds, minutes, or hours, the time portion of timestamp_exp is set to 0 before calculating the resulting timestamp.

Example: SELECT Name, {fn TIMESTAMPADD(SQL_TSI_YEAR, 1, HiredDate)} AS "Anniversary" FROM Employee

Returns:

TIMESTAMPDIFF ( interval, timestamp_exp1, timestamp_exp2 )

Instruction: Returns the integer number of intervals of type interval by which timestamp_exp2 is greater than timestamp_exp1. Valid values of interval are the following keywords: SQL_TSI_FRAC_SECOND, SQL_TSI_HOUR, SQL_TSI_SECOND, SQL_TSI_DAY, SQL_TSI_MINUTE, SQL_TSI_WEEK, SQL_TSI_MONTH, SQL_TSI_QUARTER, SQL_TSI_YEAR, where fractional seconds are expressed in billionths of a second.

Note: If either timestamp expression is a time value and the interval specifies days, weeks, months, quarters, or years, the date portion of that timestamp is set to the current date before calculating the difference between the timestamps.

     If either timestamp expression is a date value and the interval specifies fractional seconds, seconds, minutes, or hours, the time portion of that timestamp is set to 0 before calculating the difference between the timestamps.

Example: SELECT Name, {fn TIMESTAMPDIFF(SQL_TSI_YEAR, {fn CURDATE()}, HiredDate)} AS "YearsWorked” FROM Employee

Returns:

WEEK ( date_exp )

Instruction: Returns the week of the year in date_exp as an integer value in the range of 1-53.

Example: SELECT {fn WEEK({fn CURDATE()})} AS "CurWeek" FROM Company

Returns:

YEAR ( date_exp|string_exp|timestamp_exp )

Instruction: Returns the year in date_exp as an integer value.

Example: SELECT {fn YEAR({fn CURDATE()})} AS "CurYear" FROM Company

Returns:

QODBC System Functions

DATABASE ()

Instruction: Returns the name of the database in use at the time this function is called.

Example: SELECT {fn DATABASE()} AS "OpenDatabase" FROM Company

Returns:

IFNULL ( exp, value )

Instruction: If exp is null, the value is returned. If exp is not null, exp is replaced. The possible data type(s) of value must be compatible with the data type of exp.

Example: Select Name, {fn IFNULL(Fax, 'Missing Fax')} as "FixedFax" from Employee

Returns:

PARENT( string_exp )

Instruction: Returns the characters before the colon it finds in string_exp

Example : SELECT {fn PARENT(FullName)} AS “ParentValue”,FullName FROM Account CALLDIRECT

Returns:

CHILD ( string_exp )

Instruction: Returns the characters after the colon it finds in string_exp

Example: SELECT {fn CHILD(FullName)} AS “ChildValue”,FullName FROM Account CALLDIRECT

Returns:

CONVERT (integer_exp, sqltype_exp)

Instruction: Returns the slqtype value, which is converted from an integer value and can be used in numeric functions.

Example: SELECT {fn CONVERT(21,SQL_FLOAT)} AS "ConverValue", CompanyName AS "CompanyName" FROM Company

Returns:

Problem Description:

I would like to analyze how much time QuickBooks SDK takes to process the data request and how much time QODBC takes to format the data and send it back to the calling application.

This information will help us troubleshoot the slowness of the SQL statement and find the cause of the slowness.

Solution:

You can use the "sp_tablesusageinfo" command to know the time taken by QuickBooks SDK and QODBC.

The "sp_tablesusageinfo" command is available in QODBC build 353 and above.

Usage

sp_tablesusageinfo ALL

The above command will list all the tables and their statistics

sp_tablesusageinfo <TableName>

example: 

sp_tablesusageinfo Invoice

The above command will list the "Invoice" table and its statistics.

sp_tablesusageinfo <TableName> Reset

example: 

sp_tablesusageinfo Invoice Reset

The above command will reset the statistics of the table "Invoice".

LICENSE:

LICENSER grants to you a limited, non-exclusive license to (i) install and operate the copy of the computer program contained in this package ("Program") on a single computer (one central processing unit) and (ii) make archival copies of the Program for back-up purposes only for use with the same computer.

The serial number issued to you for this product indicates the QuickBooks Desktop edition year versions the QXL Desktop is licensed to use with. The serial number/registration code containing the year "24" at positions 2 and 3 is registered to work with QuickBooks 2003 or above versions as long as your QXL Desktop subscription remains in active status. If the registration code is set to "23", it will work with QuickBooks 2023 and lower versions, and so on. If the subscription status is nonactive or has been terminated for any reason, QXL Desktop will cease to continue working with QuickBooks 2024 or higher editions. If you have no serial number, you are using a 30-day evaluation version.

You agree to affix a label to the archival copies that contains the copyright notice printed on the CD-ROM from which the copy is made. LICENSER retains all rights to the Program not expressly granted in this agreement.

OWNERSHIP OF PROGRAMS AND COPIES: This license is not a sale of the original Program or any copies thereof. LICENSER retains the ownership of the program and all copies of the Program, regardless of the form in which the copies may exist. The Program and accompanying manual(s) ("Documentation") are copyrighted works of authorship, and may contain valuable trade secrets and confidential information proprietary to LICENSER. The Program and the Documentation may not be copied, modified, or transferred without the express written permission of LICENSER. You agree to exercise reasonable efforts to protect LICENSER'S proprietary interest in the Program and Documentation and maintain them in strict confidence.

USER RESTRICTIONS: You may physically transfer the Program from one computer to another, provided that it is operated only on one computer. You may not electronically transfer such Program. Versions of this product not designated as “Web Version” may not be used in a web service, time-sharing, or service bureau operation. You may not translate, modify, adapt, disassemble, decompile, or reverse engineer the Program. You may not create derivative works based on such Program or Documentation or any portions thereof.

TRANSFER: The Program is provided for use in your internal commercial business operations and must remain at all times upon premises owned or leased by you. You may not rent, lease, sublicense, sell, assign, pledge, transfer, or otherwise dispose of the Program or the Documentation, on a temporary or permanent basis, without the prior written consent of LICENSER.

TERMINATION: This license is effective until terminated. This license will terminate automatically without notice from LICENSER if you fail to comply with any provision of this license. Upon termination, you must cease all use of the program and return it, any copies thereof, including any archival copies, and the Documentation to LICENSER.

GENERAL: This license shall be governed and construed in accordance with the laws of the State of Nevada. In the event a provision of this Agreement shall be held unenforceable, it shall be deemed severable from the remaining provisions and shall in no way affect the validity or enforceability of the Agreement. The headings and captions used in this Agreement are for convenience only and are not to be considered in construing or interpreting this Agreement.

QXL - QuickBooks Data Export Made Easy
Limited Warranties and Limitation of Liability

LIMITED WARRANTY: LICENSER grants you as the original user of the Program a limited warranty that (i) the media on which the Program is distributed and the Documentation will be free of material defects for a period of NINETY (90) DAYS, and (ii) the Program will perform substantially in accordance with the material descriptions in the Documentation for a period of NINETY (90) DAYS. These limited warranties commence on the day you first obtain the Program and extend only to you, the original customer. Statements or representations which add to, extend, or modify these warranties are unauthorized by LICENSER and should not be relied upon by you. These limited warranties give you specific legal rights, and you may have other rights which vary from state to state.

DISCLAIMER: EXCEPT AS SPECIFIED ABOVE, LICENSER MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED, ORAL OR WRITTEN, REGARDING THE PROGRAM, MEDIA, OR DOCUMENTATION AND HEREBY EXPRESSLY DISCLAIMS ALL OTHER EXPRESS AND IMPLIED WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LICENSER DOES NOT WARRANT THE PROGRAM WILL MEET YOUR REQUIREMENTS OR THAT ITS OPERATION WILL BE UNINTERRUPTED OR ERROR FREE.

EXCLUSIVE REMEDY: Your sole and exclusive remedy in the event of a breach of the limited warranty set forth above is limited to either repair or replacement of the Program or the Documentation by LICENSER or refund of your money, at Licenser's sole discretion. To obtain warranty service, however, you must return the nonconforming item, with proof of the date you obtained it, to LICENSER no later than TEN (10) days after the expiration of the applicable limited warranty period. If LICENSER determines that the particular item has been damaged by accident, abuse, misuse, or misapplication or has been modified without the written permission of LICENSER, or if any LICENSER label or serial number has been removed or defaced, the limited warranties set forth above do not apply, and you accept full responsibility for the product.

LIMITATION OF LIABILITY: LICENSER AND ALL PARTIES INVOLVED IN THE CREATION OR DELIVERY OF THE PROGRAM OR DOCUMENTATION TO YOU SHALL HAVE NO LIABILITY TO YOU OR ANY THIRD PARTY FOR SPECIAL, INCIDENTAL, INDIRECT, EXEMPLARY AND CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS, GOODWILL OR SAVINGS, DOWNTIME, DAMAGE TO OR REPLACEMENT OF EQUIPMENT AND PROPERTY OR RECOVERY OR REPLACEMENT OF PROGRAMS OR DATA) ARISING FROM CLAIMS BASED IN WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT TORT OR OTHERWISE, EVEN IF LICENSER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH CLAIM OF DAMAGE. LICENSER'S LIABILITY FOR DIRECT DAMAGES SHALL NOT EXCEED THE ACTUAL AMOUNT PAID FOR THE PRODUCT.

EXCEPTIONS: Some countries and states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitations or exclusions may not apply to you. The conditions conferred by this warranty do not, however, overwrite any other rights and remedies in respect of the product which you have under applicable laws in your Country or State.

US GOVERNMENT RESTRICTED RIGHTS: The Program and Documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the US Government is subject to restriction as outlined in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause at 252.227-7013. Contractor/manufacturer is FLEXquarters.com Limited, 2620 S Maryland Pkwy Ste 14 # 557, Las Vegas, NV 89109-1692

LICENSE:

LICENSER grants to you a limited, non-exclusive license to (i) install and operate the copy of the computer program contained in this package ("Program") on a single computer (one central processing unit) utilizing a single operating system and (ii) make archival copies of the program for backup purposes only for use with the same computer.

The serial number issued to you for this product indicates the QuickBooks Desktop edition year versions the QODBC Driver is licensed to use with. The serial number/registration code containing the year "24" at positions 2 and 3 is registered to work with QuickBooks 2003 or above versions as long as your QODBC Desktop subscription remains in active status. If the registration code is set to "23", it will work with QuickBooks 2023 and lower versions, and so on. If the subscription status is nonactive or has been terminated for any reason, QODBC will cease to continue working with QuickBooks 2024 or higher editions. If you have no serial number, you are using a 30-day evaluation version.

You agree to affix a label to the archival copies that contains the copyright notice printed on the original disk or tape from which the copy is made. LICENSER retains all rights to the program not expressly granted in this agreement.
OWNERSHIP OF PROGRAMS AND COPIES: This license is not a sale of the original program or any copies thereof. LICENSER retains ownership of the program and all documents, regardless of the form in which the copies may exist. The Program and accompanying manual(s) ("Documentation") are copyrighted works of authorship and may contain valuable trade secrets and confidential information proprietary to LICENSER. The Program and the Documentation may not be copied, modified, or transferred without the express written permission of the LICENSER. You agree to exercise reasonable efforts to protect LICENSER'S proprietary interest in the Program and Documentation and maintain them in strict confidence.

USER RESTRICTIONS: You may physically transfer the program from one computer to another, provided it is operated only on one computer. You may not electronically transfer such a Program. You may not translate, modify, adapt, disassemble, decompile, or reverse engineer the program. Versions of this product not designated as "Web Version" may not be used in a web service, time-sharing, or service bureau operation. You may not create derivative works based on such Program, Documentation, or any portions thereof.

TRANSFER: The Program is provided for use in your internal commercial business operations and must remain upon premises owned or leased by you. You may not rent, lease, sublicense, sell, assign, pledge, transfer, or otherwise dispose of the Program or the Documentation, on a temporary or permanent basis, without the prior written consent of LICENSER.

TERMINATION: This license is effective until terminated. This license will terminate automatically without notice from the LICENSER if you fail to comply with any provision of this license. Upon termination, you must cease all use of the program and return it, any copies thereof, including any archival copies, and the Documentation to LICENSER.

GENERAL: This license shall be governed and construed in accordance with the laws of the State of Nevada. It shall in no way affect the validity or enforceability of the Agreement. If a provision of this agreement shall be held unenforceable, it shall be deemed severable from the remaining provisions. The headings and captions used in this agreement are for convenience only and are not to be considered in construing or interpreting this agreement.

QODBC Limited Warranties and Limitation Of Liability

LIMITED WARRANTY: LICENSER grants you as the original user of the program a limited warranty that (i) the media on which the program is distributed and the Documentation will be free of material defects for a period of NINETY (90) DAYS, and (ii) the program will perform substantially by the material descriptions in the Documentation for a period of NINETY (90) DAYS. These limited warranties commence on the day you obtain the program and extend only to you, the original customer. These limited warranties give you specific legal rights, and you may have other rights which vary from state to state. Statements or representations which add to, extend, or modify these warranties are unauthorized by LICENSER and should not be relied upon by you.

DISCLAIMER: EXCEPT AS SPECIFIED ABOVE, THE LICENSER MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED, ORAL OR WRITTEN, REGARDING THE PROGRAM, MEDIA, OR DOCUMENTATION AND HEREBY EXPRESSLY DISCLAIMS ALL OTHER EXPRESS AND IMPLIED WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LICENSER DOES NOT WARRANT THE PROGRAM WILL MEET YOUR REQUIREMENTS, OR THAT ITS OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE.

EXCLUSIVE REMEDY: Your sole and exclusive remedy in the event of a breach of the limited warranty set forth above is limited to either repair or replacement of the program or the Documentation by LICENSER or refund of your money, at Licenser's sole discretion. To obtain warranty service, however, you must return the nonconforming item, with proof of the date you obtained it, to LICENSER no later than TEN (10) days after the expiration of the applicable limited warranty period. If LICENSER determines that the particular item has been damaged by accident, abuse, misuse, or misapplication, or has been modified without the written permission of LICENSER, or if any

The LICENSER label or serial number has been removed or defaced, the limited warranties above do not apply, and you accept full responsibility for the product.

LIMITATION OF LIABILITY: LICENSER AND ALL PARTIES INVOLVED IN THE CREATION OR DELIVERY OF THE PROGRAM OR DOCUMENTATION TO YOU SHALL HAVE NO LIABILITY TO YOU OR ANY THIRD PARTY FOR SPECIAL, INCIDENTAL, INDIRECT, EXEMPLARY, AND CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS, GOODWILL OR SAVINGS, DOWNTIME, DAMAGE TO OR REPLACEMENT OF EQUIPMENT AND PROPERTY OR RECOVERY OR REPLACEMENT OF PROGRAMS OR DATA) ARISING FROM CLAIMS BASED IN WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT TORT OR OTHERWISE, EVEN IF LICENSER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH CLAIM OF DAMAGE. THE LICENSE'S LIABILITY FOR DIRECT DAMAGES SHALL NOT EXCEED THE ACTUAL AMOUNT PAID FOR THE PRODUCT.

Problem Description:

We get an error message in QuickBooks saying that the application FLEXquarters QODBC's certificate was revoked by its certification authority. I have followed the steps recommended by QuickBooks, located here: https://quickbooks.intuit.com/learn-support/en-us/help-article/web-integration/fix-error-quickbooks-application-revoked/L6Y849bKg_US_en_US?uid=llo0wp9y, but the issue persists.

I have also followed the steps from your article from 2016, located here: https://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2774/0/qodbc-desktop-troubleshooting---quickbooks-displays-a-revoked-certificate-warning, but we still have the issue.

QuickBooks SDK Logs

20230823.115249	I	17252	RequestProcessor	========= Started Connection =========
20230823.115249	I	17252	RequestProcessor	Request Processor, QBXMLRP2 v31.13
20230823.115249	I	17252	RequestProcessor	Connection opened by app named 'FLEXquarters QODBC'
20230823.115249	I	17252	RequestProcessor	OS: Microsoft Professional (build 9200), 64-bit
20230823.115249	I	17252	RequestProcessor	Current User is in AdminGroup
20230823.115249	I	17252	RequestProcessor	Current Process Integrity Level : 2000
20230823.115249	I	17252	RequestProcessor	Getting the IUnknown COM instance of QB
20230823.115249	I	17252	RequestProcessor	Opening the file in the DoNotCare mode.
20230823.115851	E	17252	RequestProcessor	Begin Session error = 80042587, Access denied by user.
20230823.115851	I	17252	RequestProcessor	Connection closed by app named 'FLEXquarters QODBC'
20230823.115851	I	17252	RequestProcessor	========== Ended Connection ==========
20230823.115954	I	17252	CertVerifier	The Authenticode signature validated OK.
20230823.115954	E	17252	CertVerifier	The certificate was revoked by its certification authority.

What are our next steps?

Reason for the issue.

We are currently not sure what is causing the issue; from our primary investigation, it seems to be either a Windows Update or a Digital Signature validator/issuer - "Symantec Class 3 SHA256 Code Signing CA" end-of-life / expired may have caused this issue.

We have reported this issue to Intuit  Support and DigiCert. We will update this page as soon as more information is available.

As per Digicert phone support, the "Symantec Class 3 SHA256 Code Signing CA" Certificate was revoked on request from Microsoft. The solution is to resign from the application.

We noticed customers using the QODBC build signed in the years 2019 and 2020 (e.g., 20.0.0.336 - 21.0.0.340) are facing this issue. If you are using QODBC version 2019 or 2020, please update QODBC to the latest version.

Installing the latest version of QODBC should resolve the issue you are facing. Please refer to the Solutions section. To receive updates on the progress of this issue, please send us an email by clicking the link provided - Click Here. You will be notified as soon as a final solution is found.

============

Email from Intuit.

Hello Intuit Developer,

We are contacting you because you have a QuickBooks Desktop application, and we believe you could be impacted by an issue with revoked certificates from the Symantec Corporation.

What is happening?

On August 22, 2023, we were notified that some third-party applications started receiving the following error message when the application tried to connect to QuickBooks Desktop:

“The certificate was revoked by the certification authority.”

After some research, it was determined that a Symantec root certificate (Symantec Corporation/DigiCert) had been revoked. On August 22, 2023, at 12:00 pm PDT, Microsoft started enforcing revocation of the certificate.

What does that mean for me?

Your application might or might not be seeing the error that the certificate was revoked. If you are not seeing this error, you are not impacted, and you can disregard this email.

If you are impacted by this issue, you can resolve it by re-signing your application and redistributing it to your customers.

Where can I get more information?

We are in the process of updating the full versions of the QuickBooks Desktop SDK and QuickBooks Web Connector (QBWC), which will be available on our QuickBooks Desktop SDK page in the next few days.

If you are having problems with QBWC, there is a patch for the latest version that can be found, along with instructions for installation, at http://intuit.me/cert. Make sure you have updated to the latest version of QBWC before applying the patch.

If you need more information about re-signing certificates from DigiCert, have a look at the Standard Code Signing certificate and Enhanced Verification Code Signing certificate documentation on DigiCert’s CertCentral.

Thank you,

============  

Solutions

You may install the latest version of QODBC to see if that resolves the issue.

If you are still facing issues, please connect with the application vendor (e.g., FileMaker, Crystal Report, VB.NET, Microsoft Excel, Microsoft Access, Alpha 5, or any Custom Application) to provide a re-signed copy of the application.

Solution 1:

Please update your application, like FileMaker, Crystal Report, VB.NET, Microsoft Excel, Microsoft Access, Alpha 5, or any Custom Application to the latest version.

If your application contains a "Digital Signature", ensure it is a valid digital certificate and has not expired.

As the vendor of your application, provide you with the latest version of the application or re-sign the existing application with the new certificate and provide you with the updated application.

Solution 2:

Workaround: Bypass the digital signature/digital certificate of your application by routing the connection via QRemote.

Existing

Your App -- > QuickBooks Data -- > QuickBooks SDK -- QuickBooks Application/QuickBooks company file.

Proposed workaround

Your App -- > QuickBooks Data QRemote -- > QRemote Server -- > QuickBooks Data -- > QuickBooks SDK -- QuickBooks Application/QuickBooks company file.

Start QRemote Server,

Start your application.

Instead of connecting to "QuickBooks Data", connect to  "QuickBooks Data QRemote."

Solution 3:

 

 

Start the command prompt (Run as administrator)

Problem Description

Upon pulling QuickBooks data into Microsoft Access, I didn’t see any values (all blank) in the QuantityonOrder field of either the Item or ItemInventory tables from QuickBooks.

Sp_report InventoryStockStatusByItem show QuantityOnOrder
Sp_report PurchaseByItemDetail

And I’ve attached a screenshot of my results for both – each showing 0 results.

I am using QuickBooks 2023.

QuickBooks SDK Logs

20230411.111122 I 30056 SpecVersion Current version of qbXML in use: 16.0
20230411.111122 I 30056 QBSDKMsgSetHandler QUERY: General Summary Report
20230411.111140 E 30056 ReportHandler::BuildTheRetObject Unable to convert column desc for column 2 since it has value 210
20230411.111140 E 30056 ReportHandler::BuildTheRetObject Unable to set the column description, HRESULT=0x80004005
20230411.111140 I 30056 QBSDKMsgSetHandler Request 1 completed successfully.

Response from QuickBooks SDK

<QBXML>
<QBXMLMsgsRs>
<GeneralSummaryReportQueryRs requestID="1" statusCode="510" statusSeverity="Warn" statusMessage="Unable to return object." />
</QBXMLMsgsRs>
</QBXML>

I have tried QuickBooks Verify & Rebuild the company file, but that did not resolve the issue.

Solutions

We have reported the issue to Intuit. Case 00129682: Unable to convert column desc for column 2 since

The issue is a bug in QuickBooks SDK - QuickBooks 2023.

Affected reports -  InventoryStockStatusByItem, InventoryStockStatusByVendor & InventoryValuationDetail

On May 26, 2023, the Intuit Team resolved the reported issue and released the fix for the issue.

Please update your QuickBooks to the latest release to fix the issue.

Updates:

Apr 18, 2023 & Apr 10, 2023 - Intuit Developer Support - "We didn't create a bug for this issue, this is a known issue. We are working on it."

"To unblock the customer as a workaround, we can disable the categories from the preferences and continue.

To locate the categories feature, go to edit->preferences->items&inventory-> Company Preferences-> under categorize items group box, uncheck "Activate categories". Impact of disabling this feature: Customer will go back to their items not being categorised as before

Turning off the Categories feature from the preferences will not have any impact on the ability to connect to the database to read inventory or any items. They will lose the ability to use the feature benefits till the fix is live.

Note: Customers have an option to turn on/off Categories as per their requirements, it’s not mandatory."

Intuit Case ID: 00129682

May 26, 2023  - Intuit Developer Support - "The fix is live, you can use the stock status report with categories."

QXL Desktop uses the QODBC Desktop driver to query QuickBooks Desktop. Commands available in QODBC Desktop will also work in the QXL desktop application.

QXL Online uses the QODBC Online driver to query QuickBooks Online. Commands available in QODBC Online will also work in the QXL Online application.

Please refer to: https://qodbc.com/links/2343.

QXL Desktop uses the QODBC Desktop driver to query QuickBooks Desktop. Commands available in QODBC Desktop will also work in the QXL desktop application.

QXL Online uses the QODBC Online driver to query QuickBooks Online. Commands available in QODBC Online will also work in the QXL Online application.

Please refer to: https://qodbc.com/links/2342

Problem Description:

How to use the QODBC Test Tool to test my SQL statement?

How to test QODBC connection with QuickBooks Data?

Solution: 

Open a company file in QuickBooks.

Start QuickBooks and open a company file, your own, or a sample company file.

Log in to QuickBooks Company File as QuickBooks user "Admin".

Using the QODBC Test Tool for testing

Running the QODBC Test Tool

     Leaving your QuickBooks company file open ->, click on Start -> All Programs -> locate the QODBC Driver for the QuickBooks program group on your desktop.

     Click on the QODBC 32-Bit Test Tool icon to launch it.

Establish a Connection

     From the first dropdown, select DSN. From the other dropdown, select the System DSN named QuickBooks Data -> Click Connect.

   This will connect you to the current company file opened by QuickBooks. If this is the first time QODBC has used this company file, you will receive a pop-up from QuickBooks asking you to allow QODBC to run. Choose the, Yes, Always option to allow the Sensitive data option.

Running test query

     Now that you have successfully established a connection to your QuickBooks data, it's time to type in your desired SQL query. Click on the Run button, and the requested query results will appear! For example, you can use the default "SELECT * FROM Customer" or type in another table like stock by entering "SELECT * FROM ItemInventory" or a stored procedure like "sp_report ProfitAndLossStandard." If you're wondering, the * in the select statement means all columns in that table.

     Alternatively, select the Show me the list of tables from the dropdown. OR type in the sp_tables command to see a list of tables available in QuickBooks.

     And when a query is displayed, if you right-click on the column heading, you can get information about the column, including whether it is updateable, insertable, size, and so on.

Disconnect

     Click the Disconnect button to disconnect.

Also, refer to 

• VB Demo is missing.

Problem Description:

How to insert data into the VendorCredit table

Solution: 

Open the "QODBC Online Test tool" from the start menu.

Click on the "Connect" button.

Used the below SQL statement to insert data into the VendorCredit table

Insert into VendorCreditItemLine(RefNumber,VendorRefListID,APAccountRefListID,TxnDate,PrivateNote,ItemLineItemRefListID,ItemLineMemo,ItemLineQuantity,ItemLineRate,ItemLineAccountRefListID,ItemLineCustomerRefListID,FQSaveToCache)
Values('TestRef','98','165',{d'2021-11-01'},'New building','36','Installation',15,100,'231','59',0)

Problem Description:

I want to export the QuickBooks data using Alteryx Designer Studio.

How can I use Alteryx Designer with the QODBC?

Solution: 

Alteryx Designer Studio is a 64-Bit application. If you are using QuickBooks 2021 and eariler, you need to use QRemote 64-Bit and configure it to use ODBC Compatibility 3.8.

64 and 32-bit words are kept separate in the Microsoft Windows Operating System. QuickBooks 2021 and older versions are 32-bit applications, so a 32-bit ODBC driver is required to communicate with them.

All versions of QuickBooks from 2002 through 2021 are built on a 32-bit architecture. In contrast, many modern applications—such as Microsoft Excel, Microsoft Access, and Microsoft SQL Server are commonly deployed in 64-bit environments.

For users running QuickBooks 2021 or earlier, this architectural difference creates a compatibility challenge: 64-bit applications cannot directly communicate with 32-bit drivers. To address this limitation, we provide QRemote.

For the users of QuickBooks 2021 or eariler, since a 64-Bit application cannot talk to a 32-bit driver, we have to do a bit of magic to get the worlds to connect, and we call it QRemote.  QRemote works as a bridge (only for QuickBooks 2022 or lower) between 64-Bit Applications and the 32-Bit QODBC Driver by communicating data calls between the two worlds using TCP/IP protocol. QRemote allows 64-Bit Web Servers and 64-Bit applications to talk to QuickBooks Live for the first time via the QODBC Driver.

For users running QuickBooks 2022 and later, this additional layer is no longer required. These versions of QuickBooks are native 64-bit applications, and the latest release of the QODBC Driver includes a fully compatible 64-bit driver. As a result, 64-bit applications can connect directly to QuickBooks (using the DSN "QuickBooks Data" ) without the need for QRemote.

QRemote Server is designed to enable connectivity and compatibility across different environments and application types. Its primary use cases include:

1. Service-Based Applications
   QRemote Server is used with service-based applications such as IIS,  SQL Server, PHP, Apache, Windows Services, Data Adapters, and other web server environments where direct interaction with QuickBooks may not be feasible.
2. Remote Connectivity
   QRemote Server allows applications running on a remote machine to connect to QuickBooks hosted on another system, enabling distributed setups and centralized QuickBooks access.
3. 32-bit and 64-bit Compatibility Bridge for QuickBooks 2021 and earlier
   QRemote Server enables 64-bit applications to communicate with 32-bit versions of QuickBooks (2022 and earlier) by bridging the architectural gap between modern applications and legacy QuickBooks environments.

QRemote has two components: “QRemote Client Driver for QODBC” and “ QRemote Server for QODBC”.

QRemote Client Driver: Allows 64-bit Applications to connect to the QRemote Server and sends the Request to the QRemote Server for Processing.

QRemote Server: Processes requested instruction from QRemote Client to QuickBooks using QODBC DSN Driver.

Setting Up a New QRemote Connection.

Start “QRemote Server for QODBC” from the start menu.

Double-click on the QRemote Server icon from the system tray.

QRemote Server Main screen will appear, that shows the IP address and Port allows the QRemote Client to connect.

Make a note of the IP address and port number listed on the QRemote Server "Event Logs " window.

Create a new DSN entry.

o Before creating A DSN entry, verify you have created a DSN entry for QODBC, which can connect to QuickBooks. 

Configure the default 64-bit DSN/or create a new 64-bit DSN

Navigate to Start Menu, QODBC Drivers for Use with QuickBooks, and click on

"Configure QODBC Data Source 64-bit" 

Navigate to System DSN and select "QuickBooks Data 64-bit QRemote" DSN and click on Configure.

Note: "QuickBooks Data 64-bit QRemote" is the default DSN created when installing QODBC.

o Under the "QuickBooks Data 64-bit QRemote"- Client DSN configuration screen, please fill in the following information

· Data Source Name: Name of your DSN entry

· Server: IP address displayed on QRemote Server

· Port: Port displayed on QRemote Server

· Encryption Key: encryption key ( keep this empty )

For the Alteryx Designer application, you need to set compatibility 3.8 in the QRemote Client.

Select 3.8 from the list and click on "Ok".

Remote DSN: Select the QODBC DSN from the list. (Make sure QRemote Server is running)

After filling in all the details, click "Test Connection" to test the QRemote connection.

Test connection is successful.

Open Alteryx Designer Studio and drag the input/output connection and drop it in the workflow screen.

Select the Input connection and click on "Connect a file or Database".

From the Data Source list, select "Generic ODBC connection".

From the Data Source name, select "QuickBooks Data 64-bit QRemote" DSN and click on "Ok".

Navigate to the Tables tab and select any table from the list, and click on the "Ok" button.

Click on the "Output Data" connection and select "Write to File or Database".

You can select any type of file connection from the screen.

Navigate to "Files" and select the "Microsoft Excel 1997-2003 .Xls."

In the dialog box, provide the file name and click on "Save".

Now, the input/output connection is ready.

Click on the "Run" button.

After running the workflow successfully, the customer data will be exported to the targeted MS Excel file.

Open your MS Excel file.

Tags: Dynamic IP Address, QRemote IP Address changes, Random QRemote IP Address 

Problem Description:

I am fetching one year of data from the QuickBooks Online General Ledger report using QODBC Online.

I get partial data/incomplete data. The expected is 30,000 records, but I got only 12910records.

Solution:

QODBC Online is able to access data from QuickBooks Online using the QuickBooks Online API, which is an embedded feature of the QuickBooks Online Application.
QODBC Online can only use those fields and commands that are allowed by the QuickBooks Online API.

Any data row limit or API limitation/restrictions of the QuickBooks Online API apply to QODBC Online.

Please refer to the question posted on Intuit Developer Forum - 

https://help.developer.intuit.com/s/question/0D50f00004lEX6qCAG/report-qbo-api-any-limits-on-the-maximum-numbers-of-rows-in-the-response

Solution:

Please change your SQL statement to fetch 3 months' data.

 Open the "QODBC Online Test tool" from the start menu.

Once the "QODBC Online Test tool" opens, select the DSN from the list and click the "Connect" button.

Use the following SQL statement. Note: We will limit the date range to three months.

"sp_report GeneralLedger show Date, TransactionType, DocumentNumber, Client, vendor, location, class, ProductService, AccountNumber, Account, Amount, Currency, ForeignAmount parameters DateFrom={d'2022-07-01'},DateTo={d'2022-09-30'}"

Click on the "Run" button to execute the query.

Note: The above query is used as an example only.

Once you can fetch three-month data, fetch another three-month data by changing the DateFrom and DataTo parameters.

Example: "sp_report GeneralLedger show Date, TransactionType, DocumentNumber, Client, vendor, location, class, ProductService, AccountNumber, Account, Amount, Currency, ForeignAmount parameters DateFrom={d'2022-10-01'},DateTo={d'2022-12-31'}"

Also, refer to 

How to connect to QuickBooks Online Sandbox

[API call limits and throttles] - https://developer.intuit.com/app/developer/qbo/docs/learn/rest-api-features

Problem Description:

I would like to rename some of my bulk items (i.e., inventory items) and their related child items (i.e., assemblies) in QuickBooks Desktop.

I found several item-related tables, item, iteminventory, iteminventoryassembly, and all of them seem to have the item number in the name field and full name.

I had assumed that the item name was only in the items table, but obviously, I was wrong.

So, do I have to change the name and full name in all item-related tables or just the item table? I guess it would have to be all tables.

Is there anything else I would need to do?

I am fairly new to QODBC and don't want to screw up the database.

Solution:

The ITEM table is a combined (read-only view) list of all Item tables in QuickBooks: ItemInventory, ItemNonInventory, ItemOtherCharge, ItemInventoryAssembly, ItemService, ItemFixedAsset, and ItemGroup; with minimum common fields.

Inserts and updates are actually done using the ItemInventory, ItemNonInventory, ItemOtherCharge, ItemInventoryAssembly, ItemService, ItemFixedAsset, or ItemGroup tables.

To update a part name, we would do:

Update ItemInventory Set Name = 'New Name' where Name = 'Old Name'

or

Update ItemInventory Set FullName = 'New Name' where FullName = 'Old Name'

or

Update ItemInventory Set FullName = 'New Name' where ListID = 'Old Name'

Problem Description

When I try to run the optimizer from the QODBC configuration screen, I get the following error when I click "Load Updated Data":

Load Updated Data did not complete (3).

When I try clicking on Reload All Data, I get its companion:

Reload All Data did not complete (3).

I tried resetting the optimizer, which was a suggested fix for what appeared to be a similar issue, but it did not work. What should I do?

Please advise.

Solutions

Please download the latest version of the QODBC Driver and try again.

If you still face the issue, please raise a support ticket - Click Here.

Problem Description

A trappable error (E06D7363) occurred in an external object. The script cannot continue running.

I receive this error when reading and writing data concurrently from two Internet Explorer windows from an ASP page. When using one browser window, the error doesn't occur. The error occurs only when there are two browsers creating connections at the same time.

Environment to reproduce the error: Windows Server OS, IIS 6.0

When running and refreshing qbcust.asp from two or more browsers located on different machines, I receive the following error message:

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File

Provider error '8000ffff'

Catastrophic failure

/Test/qbcust.asp, line 27

---------------------end output --------------------------------------------------------

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File
QODBC DSN QuickBooks Data Open
ADO Recordset Open

Customer - Outstanding Balance
*****************************
Adam's Candy Shop - $40

Active Server Pages error 'ASP 0115'

Unexpected error

/Test/qbcust.asp

A trappable error (E06D7363) occurred in an external object. The script cannot continue running.

---------------------------------end output-----------------------------------------------

The above two errors do not happen every time, but about 30% of the time, one of the two browsers will crash with either one of the above error messages. The error typically doesn't occur when running from two browsers on a web server. However, when running and refreshing two browsers on different machines, the error is easily reproduced. I checked the qodbc message log, but did not find any logs that corresponded to the time of the failure.

Please advise.

Solutions

Refer to the following articles.

If you are still facing the issue, please raise a support ticket - Click Here.

Problem Description:

I need to develop a one-off application for a client.

I have their QuickBooks Desktop company file. Can I develop on that data without having QuickBooks installed on my development machine?

If I need to purchase QuickBooks, I will buy the latest version. Will my client's 2022 company file work with that version, or will they have to upgrade as well?

Kind Regards

Solution:

This

Accounting software is unlike other software in that governments worldwide make changes all the time in relation to taxes and how people are employed and paid. A QuickBooks 2022 format company file will be converted by QuickBooks 2023 to the new format when it's opened, and there's no backward converter.

If you are going to use that company file for development only and you will not be sending it back to your client/customer, then they need not have to upgrade either QuickBooks to 2023.

Also, in my experience, there's no such thing as a one-off application. Sooner or later, you're going to have to fix, modify, change, or enhance your application because of a new business requirement. Ongoing work requires the developer to have their own QODBC license. QODBC is licensed to each computer on which it is used.

As far as what you can do when the 30-day evaluation runs out, well, you can still use a QuickBooks Sample Company file even with an expired evaluation. You can't use a real company file. After 30-Days, you can either purchase a QODBC license or use a QuickBooks sample company file.

QODBC Desktop can be used with the QuickBooks Sample company, and no QODBC license is required.

Problem Description:

Ran this SQL to move an invoice from one Customer to another:

Update invoice set CustomerRefListID = '1500' where TxnNumber = 8453

It took about 15+ minutes, and the status dialog showed it waiting on QuickBooks as it went through all 2,500 customers - but it took over 15 minutes to complete! I have a situation where moving an invoice to another Customer may occur several times in a batch of invoices. Are there additional conditions I can put in the WHERE clause that would speed this up?

Solution:

Please make sure Optimizer is enabled.  - https://qodbc.com/links/2358

If you are executing an SQL statement for the first time on this table, QODBC has built the optimizer before processing the SQL statement. "Waiting on QuickBooks" may take longer than usual.

Please run the SQL statement again, and if you are still facing the same issue, please try the following options.

Make use of the index fields, such as TxnID or TxnDate, to filter the number of records scanned.

Update invoice set CustomerRefListID = '1500' where TxnID='ValueOfYourTxnID'

or

Update invoice set CustomerRefListID = '1500' where TxnDate>={d'2022-11-10'} and  TxnDate<={d'2022-11-15'} and  TxnNumber = 8453

If you are still facing the issue, please try using the UNOPTIMIZED keyword.

Update invoice UNOPTIMIZED set CustomerRefListID = '1500' where TxnID='ValueOfYourTxnID'

Problem Description:

We have low performance in SQL Server Linked Server using QREMOTE.

For example, the below statement takes less than 2 seconds in the QODBC 64-bit Test tool and more than 2 minutes in our linked server:
UPDATE Customer SET JobTitle = 'Job3' WHERE ListID='8000000F-1466614340'.

In SQL Server, the statement seems to scan the whole table to be executed (14000 records)

We are running QuickBooks and SQL Server on the same machine on a cloud server. All drivers are 64bits. The same system DSN is used in Test Tool and in SQL Linked server: QuickBooks Data 64-bit QRemote.

Solution:

Please make sure Optimizer is enabled.  - https://qodbc.com/links/2358

Update QREMOTE...customer set JobTitle = 'Job' where ListID='8000000F-1466614340'

When you use the above query, SQL Server will fetch all the data from the Customer table. SQL Server will then apply the filter of List ID.

SQL Server will generate an update statement from the derived result and send it to QODBC/QRemote.

Thus, for a single record update, the entire table is scanned.

To avoid this, use OpenQuery and select only the record you want to update.

Please use the Index fields in the "select" and "update" clauses.

Example:
update openquery (QRemote, 'select ListID, JobTitle from Customer where ListID=''8000000F-1466614340''') set JobTitle = 'Job' where ListID='8000000F-1466614340'

Note: Here, we are using ListID (the index field) in the select statement and the OpenQuery update statement.

If you are still facing the issue, please use the UNOPTIMIZED keyword.

update openquery (QRemote, 'select ListID, JobTitle from Customer UNOPTIMIZED where ListID=''8000000F-1466614340''') set JobTitle = 'Job' where ListID='8000000F-1466614340'

Problem Description

Issue 1:

I just updated QODBC to the latest build, 349. When trying to connect to the QRemote DSN, I get the following error message.

Windows cannot find 'fqqbvsav.exe'. Make sure you typed the name correctly, and then try again.

Issue 2:

I moved everything over to a new computer and upgraded to the latest QOCBC. I can't get the connection. The latest error is windows cannot find 'fqqbvsav.exe'. Make sure you typed the name correctly, and then try again.

Reason

 The issue is caused when the QRemote Client driver cannot write to the folder. 

"C:\Program Files (x86)\QODBC Driver for QuickBooks".

The issue is reported as bug/task ID: B01491. We are working on fixing the issue.

Solutions

Solution 1:

Open the QRemote Client DSN using the ODBC Data Source. Opening the DSN configuration will create/update the necessary files in the QODBC folder.

This should fix the issue.

Please make sure you have logged into Windows as "Administrator".

QODBC Desktop

QODBC Online

QODBC POS

Please test your application now.

 Solution 2:

 If the above solution does not work, it means you do not have permission to write to the QODBC folder in the program files.

 Please contact your system administrator to either provide you with Read and write access to the QODBC folder in the program files.

Download and Install QScheduler

Please refer to the following article for how to install QScheduler - https://qxl1.com/links/3047

How to use QScheduler with QXL

QScheduler can be accessed from the Desktop.

QScheduler can also be accessed from the Windows Start Menu.

When the application starts for the first time, it will contain no tasks.

Click the "Ok" button to continue.

To create a new scheduled task, click the "Add" button.

Input the "Task Name", then click the browse button to select the application/batch file you want to run on a regular interval.

In this example, we will use the QXL Application and schedule it to export all the data of the QuickBooks company - "QuickBooks company A".

To identify the task, I am naming the task “QXL CompanyA Hourly Export”.

You can add multiple tasks if you wish to export data from various QuickBooks companies.

After the application is selected, it will automatically populate the working directory.

The ‘Working Directory’ option is useful if your application or script is looking for a file in the current folder, so you can set the current folder to where the file is.

If you wish to change the ‘Working Directory’, you may click the browse button next to the ‘Working Directory’ input box.

You can specify the command-line arguments/parameters required by your application.

In this example, I will be using the QXL Parameter file, which contains the settings being passed to the program. For more details about the QXL Parameter file, please refer to http://qodbc.com/links/2938

Input the starting time and date to begin the task and the repeat interval.

Click Close to save the task and return to the ‘Task List&rsquo.;

For QScheduler Options/Settings, click the Wrench Icon.

Enable Start QScheduler automatically when you sign in to Windows.

Click on the ‘Close’ button to close the form.

To minimize QScheduler to the System Tray, click the minimize icon.

To maximize QScheduler, click the ‘QScheduler’ icon from the system tray.

Tags: Task Scheduler for QODBC, Scheduler for QODBC Online, Run scheduled jobs

Issue:

We noticed a field or feature is not available in the QuickBooks SDK or QuickBooks API. How can I contact Intuit and request to add the missing field, report, or feature?

Method 01:

Start QuickBooks 

1. In the top menu bar, go to Help, Send Feedback Online, then Product Suggestion. 
2. Choose a Type of Feedback and Product Area (optional) from the available drop-down menus. 
3. Enter any suggestions/feedback in your Here is my suggestion: field. 
4. Select Send Feedback. 

You can also send your feedback directly to our developers by filling out our QuickBooks Feedback form. Simply enter your request/suggestions, and rest assured that all our suggested plans are subject to further study. 

Method 02:

Log in or register at https://developer.intuit.com/

Click the profile icon and then click the support icon. i.e., https://help.developer.intuit.com/s/

Click "Sign In"

Click "Sign In" again.

Under the Help menu, select "Developer Resources" and then click "Contact Support".

https://help.developer.intuit.com/s/contactsupport

Product: QuickBooks Desktop or QuickBooks Online

Category: QuickBooks API or QuickBooks SDK or SDKs or QBSDK

Existing bug list: https://help.developer.intuit.com/s/bug-tracker-page

Method 03:

QuickBooks community https://quickbooks.intuit.com/community

https://quickbooks.intuit.com/learn-support/us-quickbooks-community/misc/03/community-us

Method 04:

Also, refer to

How to enable verbose logging to see the entire request and response logs 

https://help.developer.intuit.com/s/article/QBD-QBSDK-Logging

https://help.developer.intuit.com/s/article/Understanding-QBXML-Verbose-Logs

Problem Description 1:

When running a QRemote Server or a query, the IP address changes randomly.

Solutions: 

If you are using a 32-Bit QODBC manager, please follow the steps below:

Open "QRemote Server" from the Start menu.

You will get the following screen.

Copy the computer name by clicking on the "copy button.  

Update 32-bit DSN:

Open "ODBC Data Source Administrator(32-bit)" from the start menu and switch to the "System DNS" tab.

For how to open "ODBC Data Source Administrator(32-bit)", refer to this Link - https://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2657

Select "QuickBooks Data QRemote" DSN and click on the "Configure" Button.

Note: If you are using QODBC Online, select "QuickBooks Online Data QRemote" DSN, and for QODBC POS, use "QuickBooks POS Data Qremote."

Paste the computer name in the place of the IP Address

Click on the "Test Connection" button.

Update 64-bit DSN:

Open "ODBC Data Source Administrator(64-bit)" from the start menu and switch to the "System DNS" tab.

For how to open "ODBC Data Source Administrator(64-bit)", refer to this Link - https://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/2436

Select "QuickBooks Data 64-Bit QRemote" DSN and click on the "Configure "Button.

Note: If you are using QODBC Online, select "QuickBooks Online Data 64-bit QRemote" DSN, and for QODBC POS, use "QuickBooks 64-bit POS Data Qremote".

You will get the following screen:

Past the computer name at the place of the IP Address

Click on the "Test Connection" Button.

Tags: Dynamic IP Address, QRemote IP Address changes, Random QRemote IP Address 

Issue:

We recently upgraded our Windows OS to Windows 11 and SQL Server to 2019.

We can connect from SQL Server to QODBC/QRemote.

We can execute select statements.

We are experiencing an issue when updating a record. This is working correctly in Windows 10 and SQL Server 2017. The following is the SQL statement we are using.

Update QRemote...Bill set Memo='Sent' where TxnID='12-1234-56789'

Reason:

There are some changes in the standard ODBC API in Windows OS 11 or Windows Server 2019 when using SQL Server.

The issue is caused because QODBC received the SQL statement from SQL Server.
Update QODBC.Bill set Memo='Sent' where TxnID='12-1234-56789'
instead of
update QODBC.Bill set Memo='Sent' where TxnID='12-1234-56789'

Solution:

The issue has been identified and resolved in QODBC build 346.

Please install the latest version of QODBC.

QODBC Desktop - https://qodbc.com/download/desktop

QODBC Online - https://qodbc.com/download/online

QODBC POS - https://qodbc.com/download/pos

Issue:

We created a new QODBC 32-Bit DSN with the name "QODBC-MyCompany.

The DSN was created successfully.

We tried to change the "Mode when opening" to "Single-user Mode" or "Multi-user Mode," applied the changes, and closed the QODBC Setup Screen.

The changes are not saved.

We tried changing the company file path, but the same issue.

Reason:

We have identified the issue and are currently working on the fix.

The issue is limited to the QODBC Desktop build 348.

Solution:

Please download and install the QODBC build 349 or above. - https://qodbc.com/download/desktop

Workaround:

Create a new QODBC 64-Bit DSN with the same name as your QODBC 32-Bit DSN.

After creating a 64-Bit DSN of the same name, you can apply the changes to your 32-Bit DSN.

Please raise a support ticket with us if you do not wish to apply the above workaround. We will help you with downgrading QODBC to build 345 or 346.

Click here to raise a support ticket.

You can export data using the QuickBooks Online export feature for each of the tables/reports.

There are two ways to export data from QuickBooks Online.

1) Export data using QuickBooks Online API

2) Export data using QuickBooks Online UI (browser-based application)

List of tables available through QXL Online and QuickBooks Online's Export

List of Reports available through QXL Online and QuickBooks Online's Export

Problem Description:

My MS Access application links to QuickBooks tables via the QODBC ODBC driver. The 64-bit QODBC calls the ODBC connection 'QuickBooks Data 64-Bit QRemote'. So my application is related to that name. However, on a 32-bit machine, the ODBC driver is named 'QuickBooks Data QRemote.' So when running my application on a 32-bit device, it does not find an ODBC driver with the machine name 'QuickBooks Data 64-Bit QRemote'.

So what is the best course of action? Do I name/rename the 32 and 64-bit QODBC drivers to share the same machine name? That way, the same MS Access application will work on 32 and 64-bit installations.

Or do I need to have two separate application installations? One for 32-bit and the other for 64-bit?

Solution1: 

QRemote 32-Bit

QRemote 64-Bit

Create a 32-bit QRemote DSN on the machine with the MS Access 32-bit application and name it per your requirement.

In this example, I will name the DSN - "Rockcastle."

Please refer to the link below on how to create a QRemote DSN:

How to make or configure a QRemote DSN

Please start QuickBooks and log in to your company file as QuickBooks user "Admin."

Open the MS Access application and link the tables using the QRemote 32-bit DSN "Rockcastle."

You may be prompted to accept Intuit's QuickBooks Application Certificate. Please get the certificate.

Please refer to the link below on how to link tables in the MS Access app using QODBC:

Using QuickBooks Data with Microsoft Access 2016 / 365 / 2013 32-bit

Switch to another machine with a 64-bit MS Access app.

Create a 64-bit QRemote DSN on this machine.

Use the same name for the DSN that you used for QRemote 32-bit.

In this example, it will be - "Rockcastle."

Open the shared MS Access file.

Double-click on any of the linked tables

Since the DSN Name is the same, it will automatically connect to the QRemote 64-bit DSN and fetch the data.

Solution2: 

QODBC 32-Bit

QRemote 64-Bit

Create a QODBC 32-bit DSN on the machine with the MS Access 32-bit application and name it per your requirement.

In this example, I will name the DSN - "Rockcastle."

Please refer to the link below on how to create a QODBC DSN:

How to make or configure a QODBC DSN

Please start QuickBooks and log in to your company file as QuickBooks user "Admin."

Open the MS Access application and link the tables using the QODBC 32-bit DSN "Rockcastle."

You may be prompted to accept Intuit's QuickBooks Application Certificate. Please accept the certificate.

Please refer to the link below on how to link tables in the MS Access app using QODBC:

Using QuickBooks Data with Microsoft Access 2016 / 365 / 2013 32-bit

Switch to another machine with a 64-bit MS Access app.

Create a 64-bit QRemote DSN on this machine.

Use the same name for the DSN that you used for QODBC 32-bit.

In this example, it will be - "Rockcastle."

Open the shared MS Access file.

Double-click on any of the linked tables

Since the DSN Name is the same, it will automatically connect to the QRemote 64-bit DSN and fetch the data.

Problem Description:

I am running QXL and MS Office 365.

I have tried exporting to XLSX, XLS, and even CSV format, but only the file header row writes.

Also, I am getting the following error in QXL logs:

Error Occurred: When attempting to update the value: 80000007-1539326465 - The input string was not in the correct format. Select * from Account, QXL, AdditionalInfo: table selection - Account, Table-0, Tables-151.

Solution:

Please open the 'Region Setting' and verify each 'Region setting' as formatted in the screenshots below.

Please press the 'Windows' key and type 'Region Settings' in the search bar.

Please open 'Region Settings.'

Please click on 'Related Settings.

Please click on 'Region.'

Please click on 'Additional Settings...', and it should open the 'Customize Format' window.

In the 'Number' tab, please ensure you have given input as "."(Dot) in 'Decimal Symbol,' which you can see as displayed in the screenshot below.

Using a comma or any other decimal symbol may result in a "The input string was not in a correct format" error.

Please select a 'Currency Symbol' according to your country's currency symbol in the' Currency' tab.

As per my regional settings, I have selected the UK currency symbol (£) here.

In the 'Time' tab, the 'Short Time' should be in a valid format.

Please specify the 'Short Date' format in the 'Date' tab according to your country's date format.

Please click on " Apply " and save the settings.
Please retest the same issue you are facing.

If you still face the issue, please raise a support ticket. (Click Here to submit a support ticket.)

Please attach the files listed below while submitting the ticket to analyze your issue.

1) Screenshot of QXL Application -- >Settings/Options--> About Tab
2) Screenshot of the problem you are facing. (as an attachment) - Full Screen
Share the entire log files as an attachment in text format from
3) Share>> C:\Users\yourUserName\AppData\Roaming\QXL - QuickBooks Data Export Made Easy">>Config.xml
4) QXL Logs from QXL -> Options -> Messages -> Review QXL Message Or %AppData%\QXL - QuickBooks Data Export Made Easy\QXLMessages.txt
5) QXL Logs from QXL -> Options -> Messages -> Review SDK Messages (as an attachment)
6) Which Windows OS are you using? Please share OS details.
7) Did you upgrade anything?
Please refer to How to take a screenshot: www.qodbc.com/links/screenshot.htm.

Problem Description

I tried to connect to QODBC using Python, but it gave me the following error.
Error: HY000, The driver did not supply an error! 

The Python code I am using is this. 

import pyodbc 

cn = pyodbc.connect('DSN=QuickBooks Data 64-Bit QRemote;')
cursor = cn.cursor()
cursor.execute("SELECT Top 10 Name FROM Customer")

for row in cursor.fetchall():
    print (row)

cursor.close()

cn.close() 

Solutions

Please try adding a parameter, i.e., "autocommit=True."

import pyodbc 

# pyodbc.pooling = False
cn = pyodbc.connect('DSN=QuickBooks Data 64-Bit QRemote',autocommit=True)
cursor = cn.cursor()
cursor.execute("SELECT Top 10 Name FROM Customer")

for row in cursor.fetchall():
    print (row)

cursor.close()

cn.close() 

Issue:

We upgraded our QuickBooks Enterprise from 2020 to 2022. We were using QuickBooks 2020 and the QODBC driver version 2021 without issues. QODBC wasn't working, so we upgraded and purchased a new 22 QODBC driver. We can still not get it to work after installing and buying the new driver. I am attaching screenshots of the errors.

Unable to connect QODBC to QuickBooks 2022. I followed all the directions, and still no connection. 

Reason:

"Could not start QuickBooks" after upgrading/installing QuickBooks 2022 is a known QuickBooks SDK issue.

The issue is not limited to QODBC. The problem affects all the applications that use the Intuit QuickBooks SDK. 

Solution: (Updated on 2021-11-25)

Update QuickBooks to the latest release, R3P or above.

Start QuickBooks from the main menu and click "Help" >> "Update QuickBooks Desktop."

Click "Update Now"

After the update is completed, restart QuickBooks.

QuickBooks will install the new update after starting QuickBooks again.

After the QuickBooks update is completed, restart your Windows Machine.

There are no changes required in QODBC. QODBC will automatically start working after updating QuickBooks 2022 to the latest release.

Detail (before 2021-11-25):

There are no changes required in QODBC. QODBC will automatically start working after the reported issue is fixed by Intuit.

Intuit Developer Team has observed the SDK integration issue on Windows 2012 R2, and their engineers plan to fix it for QuickBooks 2022 R3. 

Intuit team is working on fixing the issue, and the case should be resolved in the upcoming release of QuickBooks 2022.

Intuit does not yet have an ETA, but the issue might be fixed on Nov 18, 2021. 

https://help.developer.intuit.com/s/bug-tracker-page

Bug ID: QBWG-121677 and QBWG-129160

Also, refer to - After upgrading QuickBooks 2022 on Windows 2012 with QuickBooks SDK 15.0 stops working.

Workaround: 

Uninstall QuickBooks 2022 and install QuickBooks 2020 or QuickBooks 2021.

If you have already upgraded your QuickBooks company file to 2022, there is no way to downgrade the QuickBooks company file.

You may set up a temporary machine - install Windows 10 or Windows Server 2019, install QuickBooks 2022, and use it till the issue is resolved.

Once the issue is fixed, update QuickBooks 2022 on Windows Server 2012 and switch the company file to the original server.

Please follow the steps to change the auto login user associated with QODBC Certificates in the Integrated Application Under QuickBooks:

Switch the QuickBooks company file to single-user mode.

In QuickBooks ' main menu, navigate to the following menu: Edit -> Preferences -> Integrated Applications -> Company Preferences Tab.

Switch to Company Preferences

To know which application uses "FLEXquarters QODBC" to communicate with QuickBooks.

Select "FLEXquarters QODBC," Click Properties

Select the QuickBooks user from the list.

Close the Properties window.

There is no need to accept the certificate again.

Note: If multiple "FLEXquarters QODBC" are listed, you must modify all the "FLEXquarters QODBC" integrated applications.

Switch QuickBooks to multi-user mode.

Exit QuickBooks.

It is recommended to test the auto-login functionality by applying the changes.

Keywords: change security keys, application preferences, qodbc change certificate, qodbc alter permission, auto-login does not work.

Download

Please download the latest version of QScheduler from the QXL website - https://qxl1.com/qscheduler-download/.

Download the installer.

Right-click on the installer and click "Run as Administrator."

Follow the instructions below to install "QScheduler":

Click the "Next >" button.

Click the "Install >" button to start the installation.

Click the "Finish" button to complete the installation.

QScheduler can be accessed from the Desktop.

QScheduler can also be accessed from the Windows Start Menu.

Please refer to the following link: How to use QScheduler with QXL.

Problem Description:

How to use QODBC Support Wizard - Remote Connectivity?

Solution:

Please follow the steps below for using the QODBC Support Wizard.

The "QODBC Support Wizard" application is included with QODBC v18.0.0.325 and above. If you are using an older version of QODBC, please upgrade your QODBC to the latest version. Click here to download the newest version of QODBC.

The "Remote Connectivity" option is added in QODBC v21.0.0.341 

Click on the "QODBC Support Wizard" icon from the Windows Start menu.

Follow the instructions on the wizard- Please refer to http://qodbc.com/links/2981

Optional Configurations and Tests: 

Perform a remote connectivity test using QRemote 

This is an optional step.

This will help you check remote connectivity.

"Machine A" - QuickBooks Application and QODBC Driver are installed. QuickBooks company files can be on the same machine, shared drive, or another machine. In this example, the IP Address of Machine A is 192.168.137.1

"Machine B" - QODBC Driver is installed. On Machine B, the QuickBooks application is not installed.

On "Machine A" 

Start the QODBC Support Wizard on "Machine A" and make sure all the checks are passed.

Start QRemote Server on "Machine A" (if to already running)

Start QuickBooks and log in to your QuickBooks company file as QuickBooks user "Admin."

On "Machine B" 

Input the IP Address of "Machine A."

Click the "Test Remote Connection" button.

This will perform a test connection from "Machine B" to "Machine A."

If the connection fails, please check if port 4500 is open on the Windows firewall, physical firewall, and Router.

If you are behind NAT, you may have to configure Port Forwarding.

Wait for the result. Please switch back to "Machine A" to check if there is any pop-up on the QuickBooks Application.

Once the test connection is successful, you may create a DSN.

Input the "DSN Name"

Example "CompanyARemotely"

Click the "Create a new DSN" button to create a QRemote DSN on "Machine B."

You may check the DSN created via the QODBC Support Wizard using "Configure QODBC Data Source."

An SQLAlchemy dialect for the FlexODBC driver

This dialect is intended to offer an effortless way to access the DataFlex flat-file databases of older or EOL'd application-specific software. It is designed for use with the ODBC driver available from 'FLEXquarters.com'.

You can see the package page here.

Problem Description

I am using Microsoft Excel.

I am using the following SQL statement.

SELECT TransferInventoryLine.TxnDate,
TransferInventoryLine.RefNumber,
TransferInventoryLine.FromInventorySiteFullName,
TransferInventoryLine.ToInventorySiteFullName,
InventorySite.SiteAddressAddr1,
InventorySite.SiteAddressAddr2,
InventorySite.SiteAddressAddr3,
InventorySite.SiteAddressAddr4,
InventorySite.SiteAddressCity,
InventorySite.SiteAddressState,
InventorySite.SiteAddressPostalCode,
InventorySite.SiteAddressCountry,
TransferInventoryLine.Memo,
TransferInventoryLine.TransferInventoryLineQuantityTransferred,
TransferInventoryLine.TransferInventoryLineItemRefFullName,
Item.Description
FROM (TransferInventoryLine unoptimized
INNER JOIN InventorySite unoptimized
ON TransferInventoryLine.ToInventorySiteListID = InventorySite.listen)
INNER JOIN Item
ON TransferInventoryLine.TransferInventoryLineItemRefListID = Item.ListID
WHERE (TransferInventoryLine.TxnDate={d'2020-09-15'})

Solutions

We can reproduce the issue. The issue can be produced in QODBC build 336 and above.

We are working on fixing the issue.

As a workaround, please change the SQL statement.

SELECT TransferInventoryLine.TxnDate,
TransferInventoryLine.RefNumber,
TransferInventoryLine.FromInventorySiteFullName,
TransferInventoryLine.ToInventorySiteFullName,
InventorySite.SiteAddressAddr1,
InventorySite.SiteAddressAddr2,
InventorySite.SiteAddressAddr3,
InventorySite.SiteAddressAddr4,
InventorySite.SiteAddressCity,
InventorySite.SiteAddressState,
InventorySite.SiteAddressPostalCode,
InventorySite.SiteAddressCountry,
TransferInventoryLine.Memo,
TransferInventoryLine.TransferInventoryLineQuantityTransferred,
TransferInventoryLine.TransferInventoryLineItemRefFullName,
Item.Description
FROM TransferInventoryLine, InventorySite, Item
where TransferInventoryLine.ToInventorySiteListID = InventorySite.ListID
and TransferInventoryLine.TransferInventoryLineItemRefListID = Item.ListID
and TransferInventoryLine.TxnDate={d'2020-09-14'}

Click here to raise a support ticket and request if you still face the issue.

Problem Description

I have purchased the QODBC Server edition license 2021.

I have activated the QODBC 2021 Server edition license on the machine on which I have my service-based application (SQL Server).

When creating a linked server, I get the following error message.

"QODBC Server Edition License Required. Please visit qodbc.com/links/needserverlicense."

Solutions

We can reproduce the issue.

The issue is limited to the QODBC 2021 Server edition license.

The reported issue is fixed in QODBC v21.0.0.340. It is recommended to use the latest version of QODBC. To know about the latest version of QODBC, please visit http://qodbc.com/download.htm

Please download the latest version of QODBC. http://qodbc.com/download.htm

If you are still facing the issue, please raise a support ticket.

Click here to raise a support ticket.

     Manual License synchronization (Manual License Sync) can be used for computers that do not have direct Internet access or where the automated activation fails.

Click on Start -> All Programs -> locate the QODBC Driver for use with the QuickBooks POS program group on your desktop. Click on the Configure QODBC POS Data Source icon to launch the setup program.

Select the Activate/Deactivate tab page in the QODBC Setup screen and click on the License Sync button.

Copy the information from your computer screen. Click on the hyperlink or the Copy button.

Visit the URL: http://www.qodbc.com/QODBCPOSManualLicenseSync.html

Enter the Serial Number, Request Code, and Software ID.

Click on the Process to generate a code to verify your QODBC POS license.

If you have correctly entered your Serial Number, Request Code, and Software ID, your activation will now be processed.

   On the computer with QODBC Online installed, copy and enter your Verification No. And the Activation Code from the above image, and click on the Sync Now button when done.

Click OK to continue.