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)

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

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 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 

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.

     Locate the QODBC Driver for the QuickBooks program group on your desktop. Click on the ODBC Data Source icon to launch the setup program supplied with QODBC.

     Please refer to How to locate Configure QODBC Data Source?

     Please navigate to System DSN, select the QuickBooks Data DSN, and then configure it.

.

     The following General setup screen will become available.

.

     Please switch to the Optimizer tab page.

Switch OFF the QODBC Optimizer

     Uncheck the Use Optimizer option. Read the location for your Optimizer Database Folder and delete the YourCompanyName.opt file using Windows Explorer:

The default location of the.OTP file is in your login user profile (%AppData%\QODBC Driver for QuickBooks\Optimizer) & delete the.OPT file.

     Leave the Use Optimizer option unchecked to leave the Optimizer off.

RESET the QODBC Optimizer

     Where are the Optimizer options? Where are the Optimizer options? Check the Use Optimizer option to reactivate and reset the Optimizer. See also: How do I set up the QODBC Optimizer?

     Note: You can also schedule complete optimization overnight using QODBCFUL.EXE or QODBCUPD.EXE. Both set the error level variable if errors are detected, and error messages are written into the log file. Passing a DSN on the command line to these programs will choose the QuickBooks company file you wish to use.

    To temporarily bypass your optimizer settings and extract the latest information, you can add the unoptimized tag after the table name, like this, to your queries:

    select * from InvoiceLine unoptimized where TxnDate >= {d'2006-03-06'}.

    Or you can resync your optimizedInvoiceLine table by running:

   sp_optimizefullsync InvoiceLine

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.

Deactivate QODBC Online from your computer

You can deactivate the QODBC Online license from:

Start >> All Programs >> QODBC Driver for QuickBooks Online>> Configure QODBC Data Source

Go To "System DSN" Tab>> Select "QuickBooks Online Data">> click "Configure"

Switch to the Activate/Deactivate tab >> click "Deactivate."

     Enter your 16-digit CD Key (with the dashes) and click on the Deactivate button.

Manual Deactivation

Note: Manual Deactivation can be used for computers that do not have direct Internet access or where the automated deactivation fails.

      Copy the information from your computer screen (not the example shown here) into the image directly below and click on Process to generate a code to deactivate QODBC Online. Click on the Copy Information to the Clipboard button to save your CD Key.

      If you have correctly entered your CD Key, Request Code, and Software ID, your deactivation will now be processed. Click on the Manual button on the computer that has QODBC Online installed and copy and enter your Serial Number, Name, Request Code, and Deactivation Code from the above image, and click on the Deactivate button when done.

     If you have entered the information incorrectly, you will receive a "CD Key not found" message.

     Clicking on the Deactivate button will generate a verification number.

     Copy the information from your computer screen (not the example shown here) into the image directly below and click on Process to confirm your deactivation of QODBC Online.

     Once you process your verification number, your copy of QODBC Online will then be successfully deactivated on your computer so that you can transfer the license to your new computer! See: How to activate QODBC Online to activate the license on your new computer.

     Click Cancel to exit the QODBC Online Setup screen.

Note: Using the latest version of QODBC, credit for deactivation CDKEY is received instantly. In some cases, deactivation may take between 24 and 48 hours, depending on your region and license pack.

Problem Description:

How to export QuickBooks Data to Google Sheets using QXL

Solutions: 

Install the Google Drive desktop application and authorize it to connect to your Google Drive account.

Start Windows Explorer and navigate to your local Google Drive folder.

Create a QXL folder in Google Drive.

Start QXL Desktop and click on Settings.

In the "General" tab, set the path to the "Google Drive" path in the "Output folder."

For Example- C:\Google Drive\QXL

Close settings

Export the QuickBooks Data

Once the export is complete, the output folder showing the list of files will open automatically.

The output folder will contain the list of exported files.

The exported files will be automatically uploaded to Google Drive.

Open your web browser and navigate to - drive.google.com.

Navigate to the QXL folder.

You will find your QuickBooks company file folder.

Double-click the QuickBooks company folder to view the list of exported files.

To preview the file, double-click on any of the files.

In preview mode, you will not be able to change/modify any records.

To edit any file, go back to the preview.

Right-click on the selected file, and in the "Open with" option, select "Google Sheets."

Tags: QXL Desktop, Google Sheets

Problem Description:

Missing QODBC Menus in the Start Menu

Solutions: 

Navigate to the path: C:\Users\Administrator

In the Administrator folder, you will see the following options.

Switch to the 'View' tab in the menu bar and tick the checkbox 'Hidden items' option.

You will find the folder named 'AppData.'

After locating the AppData Folder, navigate further to the path:

AppData\Roaming\Microsoft\Windows\Start Menu\Programs

You will find the folder "QODBC Driver for use with QuickBooks."

Copy the folder "QODBC Driver for use with QuickBooks."

Navigate to the path below:

C:\Users\YOURUSERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs

It would be best if you replaced YOURUSERNAME with your Windows UserName.

In this example, we will take 'Ricky' as the Windows UserName.

C:\Users\Ricky\AppData\Roaming\Microsoft\Windows\Start Menu\Programs

Paste the copied folder to this location.

You will need Administrator Permission to paste the folder.

Click "Continue" to move ahead with pasting the copied folder.

Click the Windows Start button to check if you can view the QODBC menu.

Tags: QODBC Menu, QODBC Users, Administrator user

Problem Description 1:

I have the latest driver version and no errors during installation. When I tried to connect, it just stuck on "connecting."

Problem Description 2:

We installed the trial QODBC for the workstation. We cannot connect to our company file using 'test connection.' QODBC and QuickBooks hang, but can be closed with the task manager.

Problem Description 3:

The QODBC driver passes the Test Connection to QuickBooks after the initial install.

Shortly after, the initial install stops working.
The Test Connection to QuickBooks button hangs.
The screen says Not Responding.
He hangs until the task is killed.

Solution:

Please follow the steps below.

1) Remove Optimizer file(s)

Click the Windows Start button >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source. Go to the "System DSN" Tab, select "QuickBooks Data" DSN & click "Configure". Switch to the Optimizer tab & Click Reset Optimizer File(s)

You may also refer How to Remove Optimizer file.


2) Please verify that the Optimizer File(s) are deleted.

You can find the optimizer folder path from QODBC Setup Screen-> "Optimizer" tab.

The default path: "%appdata%\QODBC Driver for QuickBooks\Optimizer."
For Example, C:\Users\YOURNAME\AppData\Roaming\QODBC Driver for QuickBooks\Optimizer.

3) Please enable the QODBC status panel

Click the Windows Start button >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >> Go To the "System DSN" Tab, select "QuickBooks Data" DSN & click "Configure">> Navigate to Message tab->Select "Display Driver Status" and "Display optimizer Status" options.

You may also refer to How to view details on what QODBC is performing / Display Driver Status / Display optimizer Status.

4) Please try to connect to QuickBooks using QODBC Support Wizard. 

5) Optional - Rebuild the Optimizer file(s)
For more details, please click here. Refer to section "3. Rebuild Optimizer file."

Problem Description

• How does QODBC validate all the business logic that is part of the QuickBooks application?
• Can QODBC read or write directly to the QuickBooks company file (.QBW or . QBB)?

Solution

QODBC works as a Windows ODBC driver (DLL) to access the QuickBooks data. QuickBooks Accounting stores its data in its own proprietary encrypted file system.

Due to the nature of accounting systems, balancing, and transaction integrity, the QuickBooks system prevents all external applications from directly accessing the data files used by QuickBooks. However, Intuit created a workaround called the QuickBooks SDK (software development kit), which resides inside the QuickBooks application interface.

QODBC allows users of any ODBC-compliant front-end application to read and write data contained in the QuickBooks system, similar to any other ODBC-enabled database, by processing commands via the QuickBooks SDK interface in the desktop application, so QODBC will not run if QuickBooks is not installed on the same machine or a connected machine (see: QRemote) because the SDK resides in the application
itself.

QODBC accepts SQL (structured query language) commands from applications through the ODBC interface, then converts those calls to navigational XML commands, passing them to the QuickBooks SDK for processing and returning recordsets that qualify for the query results.

This driver is not a Client/Server product or a direct database access tool because that method is prohibited by Intuit, but rather communicates directly with the QuickBooks application as it runs.

QuickBooks is a flat-file database; this driver will not change it into a relational database, so keep that in mind when developing with this driver.

QODBC acts as a 'wrapper' around the Intuit SDK so customers can finally get at their QuickBooks data using standard database tools, speeding development time.

QODBC does not write to the QuickBooks company file directly. QODBC is writing through the QuickBooks SDK, which follows all business rules & validation.

Note: QuickBooks requires you to approve the security settings for QODBC to allow it to access the data in QuickBooks once for each application/company file combination. After this step, the connection to data in QuickBooks can be fully automated and does not require user input.

Tags: QuickBooks start, QuickBooks autostart, QuickBooks startup, QuickBooks connect, Hidden QuickBooks, Quiet QuickBooks, Silent QuickBooks, Background QuickBooks, How to setup QODBC for Auto-login into QuickBooks, a process for automatically start of QuickBooks, QuickBooks automatic, automatic quick books, autostart QuickBooks, automatically start of Quickbooks, running QuickBooks automatic, autologin, connection to data does not work unless Quickbooks is running even though I have that option turned on in the QODBC control panel, how to run without QuickBooks

Problem Description:

How to use the QODBC Support Wizard?

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.

OR Click here to download "QODBC Support Wizard." 

Click on the "QODBC Support Wizard" icon from the Windows Start menu.

"QODBC Support Wizard" is open. Click "Next."

Follow the instructions on the wizard.

On the QODBC DSN Verification step, make sure it passes all the checks.

In case you see a warning icon below. Please click the "FIX" button so the QODBC Support Wizard can automatically fix the issue.

Once the QODBC Support Wizard has performed all checks, please click the "Next" button.

Once the QODBC Support Wizard has performed all checks, please click the "Next" button.

Now, click the "Test Connection" button.

On clicking the "Test Connection" button, you will notice "Connecting to QuickBooks" as shown below.

When QODBC tries to access the company file for the first time, QuickBooks will ask you for permission to allow the driver to access your QuickBooks company file. Switch to the QuickBooks application & accept the certificate.

OR

After accepting the Application Integration certificate, the QODBC Support Wizard should be able to connect to QuickBooks and should report "Test connection successful."

Click the "Next" button, select the default option "Yes, I can connect to QuickBooks," and click "Next."

You may click one of the options on the "Optional Configurations" steps. The default is "I can connect and would like to skip optional configuration/tests."

Click "Next" to navigate to the Finish window.

Testing your SQL Statement:

Start the QODBC Support Wizard from the Windows Start menu.

Click "Test my SQL commands in QODBC directly."

You may test connectivity and the data fetch on the "Test your SQL statements" steps. Click one of the five buttons, write your SQL statement, and click "Query."

Detailed explanation of each check

QODBC latest version check 

This step will check if your machine is installed with the latest QODBC version available on the website.

If your QODBC version is lower than the latest version, it will show a warning/failure mark.

To fix the issue, click the "FIX" button, and you will be navigated to the QODBC website to download the latest QODBC version.

(Note: Internet connectivity is required.

QuickBooks check (Multiple versions of QuickBooks installation) 

This step will check for multiple versions of QuickBooks installed on your machine.

If multiple QuickBooks are installed, you may not be able to use the QODBC Auto-login feature. This is because QODBC uses QuickBooks SDK to work with QuickBooks, and QODBC /QuickBooks SDK will not be able to judge from the company file path to determine which edition of QuickBooks to start.

For Example:

You have QuickBooks 2018 and QuickBooks 2020 installed on your machine.

You have created two DSNs to access the QuickBooks Company file 2018 and 2020 data.

When you auto-connect with the QuickBooks company file 2018, the QuickBooks SDK will not be able to identify which QuickBooks version to start. Hence, it may begin QuickBooks 2020 in the background (since QuickBooks 2020 is the latest QuickBooks version, it will start by default).

The solution is to keep the QuickBooks application running so that the QODBC / QuickBooks SDK does not have to load QuickBooks and can connect to an existing instance.

Or

If you are using only one of the QuickBooks versions, you may uninstall the non-required QuickBooks version.

QRemote Server firewall check 

This step will check whether incoming or outgoing connection requests from the QRemote Server port number are allowed via your Windows firewall.

If there is no entry of the QRemote Server port number 4500 in the firewall, then it will create one in the allowed list.

If you have selected disallowed in the firewall for connection requests coming from or to the QRemote Server port number 4500, then it will not alter those settings. You will need to change it manually.

QuickBooks and QODBC major version check 

This step will check whether your QODBC license OR version is higher than or equal to the QuickBooks version.

If your QODBC license or version is lower than the QuickBooks version, it will show a warning/failure mark.

For Example:

If you use QuickBooks 2020 and have QODBC version 2019, it will show a warning/failure mark.

Or

If you have QuickBooks and the QODBC version is 2020, the QODBC version is 2020, but your QODBC license is 2019, it will show a warning/failure symbol.

To fix this, you will need to activate the QODBC license and the version equal to or higher than QuickBooks.

Office 32/64-bit – QODBC license compatibility check 

This step will check whether you have a compatible QODBC license to work with MS Office 64-Bit.

If you do not have a QODBC license and are using MS Office 64-Bit, it will show a warning/failure symbol.

Once you have purchased and activated the QODBC license, the validation check will change to a green tick mark.

If you don't want to use MS Office 64-bit or purchase a QODBC license, you may switch to MS Office 32-bit.

Click on the "FIX" button and follow the instructions.

Or

Please refer to the link below on how to convert 64-bit to 32-bit MS Office:

http://qodbc.com/links/3000

QuickBooks check (Elevated Mode – Run as Administrator) 

This step will show a warning/failure symbol if your QuickBooks application runs under elevated permissions or as "Run as administrator."

The QuickBooks application and your application, like Microsoft Excel, Microsoft Access, or your custom application, should be running under normal/standard user mode.

For further instructions, click on the "FIX" button and follow the instructions.

Or

You may navigate to the following link:

http://qodbc.com/links/2529

Optional Configurations and Tests:

Set up Auto-login in QuickBooks 

This is an optional step.

This will help you create a QODBC DSN for Auto-login.

QODBC Support Wizard can create a new DSN and configure it to auto-login to QuickBooks.

Click the "Browse" button, provide a DSN Name (in case you want to change the auto-generated DSN name), and click "Create a new DSN."

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

Click "Test QODBC Connection"

Company file path – Specify the QuickBooks company file path for which you wish to configure Auto-login.

You may use the "Browse" button to locate the QuickBooks Company file.

or

You must copy the QuickBooks company file path and paste it into this field. You can find the QuickBooks company file path in the QuickBooks UI (press F2 in QuickBooks UI).

DSN Name – Once you have specified the company file path, the QODBC Support Wizard will automatically generate a DSN name based on your QuickBooks company file name.

For Example:

Suppose the QuickBooks company file name is "sample_product-based business.qbw" (refer to the image).

The wizard will generate a DSN Name – "sample_product-based bu" (refer to the image).

If you want to change it, you may create a new DSN Name per your requirement.

Test QODBC connection – Click on this button to test the QODBC connection to connect to your QuickBooks company file.

Test QRemote connection - Click this button to test the QRemote connection to connect with your QuickBooks company file.

Repeat the above steps to create multiple DSNs if you have numerous companies.

Rebuild the QODBC Optimizer file. 

This is an optional step.

This will help you reset and rebuild your QODBC Optimizer files.

QODBC Support Wizard can reset and rebuild the QODBC optimizer file.

Click "Reset Optimizer Files" to delete the existing QODBC Optimizer file.

Click "Optimize All Tables" - This will start the process and rebuild the entire optimizer file for the opened QuickBooks company file.

This process may take a few hours (4 to 24 hours), depending on the number of records in your QuickBooks company file.

Reset optimizer files – When you click this button, your QODBC Optimizer file will be deleted from the Optimizer folder.

It will ask for confirmation. On confirmation, the optimizer file will be deleted.

If you have multiple QuickBooks company files, it will ask for confirmation for each optimizer file.

Once you have reset/deleted the optimizer file, you can optimize all or the selected QODBC data tables.

Optimize All Tables – If you want to optimize all tables, click on this button.

Or

Optimize Selected Tables – If you want to optimize selected tables, then click on this button.

From the list of tables, select the tables you want to optimize.

For Example:

To optimize Bill, Invoice tables, select Bill, Invoice tables, and then click "Optimize Selected Tables."

QRemote connectivity test 

This is an optional step.

QODBC Support Wizard can also perform a "QRemote Test Connection" to check if QRemote is configured correctly and can connect.

Troubleshooting with QODBC Support Wizard:

If you cannot connect to QuickBooks, select "No, I am not able to connect to QuickBooks" and click "Next."

You may link one or more relevant topics from the FAQs and Knowledgebase, or search our knowledge base using the search button.

If you are still facing the issue, report the problem to us by creating a support ticket.

Also, refer to How to use QODBC Support Wizard - Remote Connectivity.

There is no difference in the commands, queries, data, or schema between the QODBC Server Edition license and the QODBC Read/Write license.

QODBC is a client-side driver that typically resides on the workstations/client machine(s).

QODBC Server edition license is required when you have any service-based application like SQL Server, Web Server, and Windows Service connecting to QODBC or installing QODBC on a Terminal Service/Remote Desktop Service enabled machine.

QODBC license depends on the application you want to use. When the machine uses services like a web server, PHP, MS SQL Server, Windows task scheduler, and connecting to QRemote/QODBC needs a server license.

So, if you are using any service-based application, you need QODBC Server Edition.

If you want to use a desktop-based application like MS Access or MS Excel and access read-only, you need a QODBC Read Only license.

If you want to use a desktop-based application like MS Access or MS Excel and you want read-write access, then you need a QODBC Read-Write license.

QODBC licensing is machine-wise. QODBC licensing is machine-wise. You need to buy a license QODBC/QRemote for each workstation you want to use the QODBC/QRemote driver(s). If you have a QODBC Server Edition license activated on your Server, your workstations, if using QODBC/QRemote driver(s) directly, will still need a QODBC License.

Also, refer to the following:
QODBC Licensing Information
QODBC with QRemote Licensing Information

When you install QODBC Online below menu items are created under QODBC Driver for use with the QuickBooks Online folder in the Start menu.

1. Configure QODBC Online Data Source 64-bit

Configuring the QODBC Online Data Source 64-bit option will help you to create/configure a QRemote 64-bit DSN, which is used in the 64-bit application.  

2. Configure QODBC Online Data Source

Configuring the QODBC Online Data Source option will help you to create/configure QODBC & QRemote 32-bit DSN, which is used in the 32-bit application.  

3. Purchase QODBC Online Now

The purchase QODBC Online Now option will navigate you to the QODBC website for purchasing a QODBC Online license.  

4. QODBC Online Quick Start Guide

The QODBC Online Quick Start Guide option will open a start guide that will guide you on how to use QODBC Online.  

5. QODBC Online Setup Screen

The QODBC Online Setup Screen option will help you configure different setup options in QODBC Online.  

6. QODBC Online Support Wizard

QODBC Online Support Wizard is a tool available with QODBC, which is useful in testing the connection with QuickBooks. QODBC Online Support Wizard is verifying the configuration to connect to QuickBooks, which will help fix the issue. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks Online\QSW\QODBCSupportWizard.exe

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks Online\QSW\QODBCSupportWizard.exe

7. QODBC Online Test Tool

QODBC Online Test Tool is a tool available with QODBC that is useful in testing queries with QuickBooks. QODBC Online Test Tool can also perform insert/update/delete operations using standard SQL language.

8. QRemote Server for QODBC Online

QRemote Server for QODBC Online will help you start QRemote Server if it is not running.  

9. QuickBooks Online Table Schema

The QuickBooks Online Table Schema option will navigate you to the QuickBooks Online Table Schema/Data Layout page.  

10. README File

README File option will open a README file containing instructions on how to install the QODBC Online, how to use the essential functions of the QODBC Online, and what the QODBC Online does. It also includes a list of recent updates made to the QODBC Online.  

11. Uninstall QODBC Online

Uninstalling the QODBC Online option will uninstall QODBC Online from the system. If you are updating the QODBC Online version, then you need to uninstall the older QODBC Online version & install the newer QODBC version. At that time, uninstalling the QODBC Online option will help you.  

12. VB Demo

VB Demo is a tool available with QODBC Online, which is helpful in testing connections with QuickBooks Online. VB Demo is also useful for querying table data. VB Demo can also perform insert/update/delete operations using standard SQL language.

Tags: QuickBooks Online, QBO, QODBC Online menu, configure QODBC Online

When you install QODBC POS below menu items are created under the QODBC Driver for use with the QuickBooks POS folder in the Start menu.

1. Configure QODBC POS Data Source 64-bit

Configure QODBC POS Data Source 64-bit option will help you to create/configure QRemote 64-bit DSN, which is used in the 64-bit application.  

2. Configure QODBC POS Data Source

Configuring the QODBC POS Data Source option will help you create/configure QODBC & QRemote 32-bit DSN used in the 32-bit application.  

3. Purchase QODBC Driver for QuickBooks POS

The purchase QODBC POS Now option will navigate you to the QODBC website for purchasing a QODBC POS license.  

4. QODBC Driver for QuickBooks POS Quick Start Guide

QODBC Driver for QuickBooks POS Quick Start Guide option will open a start guide that will guide you on how to use QODBC POS.  

5. QODBC POS Setup Screen

THE QODBC POS Setup Screen option will help you to configure different setup options in QODBC POS.  

6. QODBC POS Support Wizard

QODBC POS Support Wizard is a tool available with QODBC, which is useful in testing the connection with QuickBooks. QODBC POS Support Wizard is verifying the configuration to connect to QuickBooks, which will help fix the issue. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks POS\QSW\QODBCSupportWizard.exe

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks POS\QSW\QODBCSupportWizard.exe

7. QODBC POS Test Tool

QODBC POS Test Tool is a tool available with QODBC that is useful in testing queries with QuickBooks. QODBC POS Test Tool can also perform insert/update/delete operations using standard SQL language.

8. QRemote Server for QODBC POS

QRemote Server for QODBC POS option will help you to start QRemote Server if it is not running. Note: QRemote Server has started automatically on system startup.  

9. README File

The README File option will open a README file containing instructions on installing the QODBC POS, how to use the QODBC, and what the QODBC POS does. It also includes a list of recent updates made to the QODBC POS.  

10. Uninstall QODBC POS

Uninstalling the QODBC POS option will uninstall QODBC POS from the system. If you are updating the QODBC POS version, you need to uninstall the older QODBC POS version & install the newer QODBC POS version. At that time, the Uninstall QODBC option will help you.  

11. VB Demo

VB Demo is a testing tool available with QODBC POS, which is helpful in testing the connection with QuickBooks POS. VB Demo is also a valid query table for data. VB Demo can also perform insert/update/delete operations using standard SQL language.

When you install QODBC, the following menu items are created under QODBC Driver for use with the QuickBooks folder in the Start menu.

1. Configure QODBC Data Source 64-bit

Configure QODBC Data Source 64-bit will help you to view/create/configure 64-bit DSNs like "QuickBooks Data 64-bit QRemote" or "QRemote Data 64-bit". 64-bit DSNs are used by the 64-bit application(s). You can run the 64-bit ODBC admin utility to see the data source from:
C:\Windows\System32\odbcad32.exe 

2. Configure QODBC Data Source

Configuring the QODBC Data Source will help you to create/configure QuickBooks Data & QRemote 32-bit DSN, which is used in the 32-bit application. You can run the 32-bit ODBC admin utility to see the data source from:
C:\Windows\SysWOW64\odbcad32.exe 

3. Purchase QODBC Now

Purchase QODBC Now will navigate you to the QODBC website for purchasing a QODBC license. 

4. QODBC Quick Start Guide

QODBC Quick Start Guide will open "QODBC Quick Start Guide.pdf." The Quick Guide document should help you get started and use QODBC. You can find information regarding how to use QODBC for the first time, samples, FAQ & support information. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\QODBC Quick Start Guide.Pd

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\QODBC Quick Start Guide.Pdf

5. QODBC Setup Screen

QODBC Setup Screen will help you to configure different setup options in QODBC. You can perform different configurations from the QODBC Setup Screen, like setting up auto-login to QuickBooks, checking QODBC & QuickBooks SDK logs, setting up the Optimizer option, and configuring other Advanced Setup options. 

6. QODBC Support Wizard

QODBC Support Wizard is a tool available with QODBC that is useful in testing the connection with QuickBooks. QODBC Support Wizard is verifying the configuration to connect to QuickBooks, which will help fix the issue. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\QSW\QODBCSupportWizard.exe

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\QSW\QODBCSupportWizard.exe

Please refer to the How to use QODBC Support Wizard

7. QODBC Test Tool

QODBC Test Tool is a tool available with QODBC that is useful in testing queries with QuickBooks. QODBC Test Tool can also perform insert/update/delete operations using standard SQL language.

8. QRemote Server for QODBC

QRemote Server for QODBC will help you to start QRemote Server if it is not running. Note: QRemote Server has started automatically on system startup. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\QRemote\Server\QRemoteServer.exe

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\QRemote\Server\QRemoteServer.exe 

9. QuickBooks Table Schema

QuickBooks Table Schema will navigate you to the QuickBooks table Schema/Data Layout page, using that link. You can get details about the QODBC table & report schema. You will get information on each table's relation with other tables, table/report columns, and report parameters that are supported.  

10. README File

README File will open a README file containing instructions on how to install the QODBC, how to use the basic functions of the QODBC, and what the QODBC does. It also includes a list of recent updates made to the QODBC. Link location:
For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\readme.rtf

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\readme.rtf

11. Uninstall QODBC

Uninstalling QODBC will uninstall QODBC from the system. If you are updating the QODBC version, you need to uninstall the older QODBC version & install the newer QODBC version. At that time, uninstalling the QODBC option will help you. Link location:

For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\UNWISE32.EXE

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\UNWISE32.EXE

12. VB Demo

VB Demo is a tool with QODBC that is useful in testing the connection with QuickBooks. VB Demo is also useful for querying table data. VB Demo can also perform insert/update/delete operations using standard SQL language. Link location:

For 32-bit System:
C:\Program Files (x86)\QODBC Driver for QuickBooks\VBDEMO32.EXE

For 64-bit System:
C:\Program Files\QODBC Driver for QuickBooks\VBDEMO32.EXE

First, you need to create a Linked Server in SQL Server.

For 32-bit SQL Server. Please refer to How to create Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC/QRemote.

For 64-bit SQL Server. Please refer to How to create Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC/QRemote.

I have already created a linked server, "QRemote."

After creating a Linked Server, you need to create a new database in SQL Server for creating the stored procedure which accepts SQL queries. The stored procedure will call the linked server and execute the query.

To create a database, you need to right-click on "Database" & click on "New Database."

Enter the database name & click "OK." In this example, I am creating the database "QODBC."

Database created.

Now, we will create a stored procedure that accepts SQL queries. The stored procedure will call the linked server and execute the query.

In Object Explorer, connect to an instance of Database Engine and then expand that instance.

Expand Databases, expand your database, and then expand Programmability.

Right-click Stored Procedures, and then click New Stored Procedure.

We will create two stored procedures first one will give us a list of all customers & second procedure will accept SQL queries through parameters & execute them on the linked server & provide the query result.

We will create the stored procedure named GetCustomer, which will query the Customer table through the linked table in SQL Server & provide a list of the customers.

Stored Procedure Created.

Stored Procedure Code:

================================================================
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

CREATE PROCEDURE GetCustomer

AS
BEGIN
SET NOCOUNT ON;

SELECT * from QRemote...customer

END
GO
================================================================

Note: The above-stored procedure code is, for example. You can change it as per your requirement.

By executing this stored procedure, we will get a list of the Customers.

We will create a second stored procedure named QODBCQuery, which will accept an SQL query through parameters & execute on the linked server & provide the query result.

Stored Procedure Created.

Stored Procedure Code:

================================================================
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

Create PROCEDURE QODBCQuery

@sqlQuery nvarchar( 4000)

AS
BEGIN
SET NOCOUNT ON;

DECLARE @TSQL varchar(8000)
SELECT @TSQL = 'SELECT * FROM OPENQUERY(QRemote,''' + @sqlQuery + ''')'
EXEC (@TSQL)

END
GO
================================================================

Note: The above-stored procedure code is, for example. You can change it as per your requirement.

We must pass the query as the parameter value to execute this stored procedure.

Query results through the stored procedure.

Now, we will create a SQL Server DSN on the non-SQL Server machine to access QuickBooks Data remotely via SQL Server.

Locate the QODBC Driver for the QuickBooks program group on your desktop. Click on the Configure QODBC Data Source icon to create a SQL Server DSN.

Click on the System DSN tab to create a DSN that both Windows applications and services can call. Click on the Add button to create a new DSN.

Select SQL Server & click "Finish."

Enter the DSN name and SQL Server machine IP address & click "Next."

Select the authenticity of SQL Server & click "Next."

Select the SQL Server database where we have created the stored procedure & click "Next."

Click "Finish."

Click on "Test Data Source..." to test the connection.

Test connection success.

Note: If you are using the latest version of QODBC, you can use the "QODBC 64-Bit Test tool."

Open the "QODBC 64-Bit Test tool" from the start menu.

Click on the "Drop-down Menu" button.

Select DSN from the Drop-down list.

For example: "QuickBooks Data 64-Bit QRemote."

Click on the "Connect" button.

Write down the query in the marked field. Please refer to the image.

Click on the "Run" button.

Note: The above Query is, for example. You can change it as per your requirement.

First, you need to create a Linked Server in SQL Server.

For 32-bit SQL Server. Please refer to How to create Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC/QRemote.

For 64-bit SQL Server. Please refer to How to create Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC/QRemote.

I have already created a linked server, "QRemote."

After creating a Linked Server, you need to create a stored procedure, which will read data from the Linked Server table & write it into the SQL Server local table.

For storing Linked Server data in the local database. It would be best if you used the INSERT INTO SELECT query as below.

For Example:

SELECT * INTO SQL_Local_TableName FROM YourLinkedServerName...TableName;

First, we will add a single table in the local database. After that, we will create a stored procedure for all tables

We will add an Account table in the local database with the table name as Tbl_Account.

SELECT * INTO Tbl_Account FROM QRemote...Account

The Tbl_Account table is created for the local database with 105 records.

Now we will query the local table Tbl_Account.
Select * from Tbl_Account
Data is available in the local database table.

Now, we will create a stored procedure that will read data from the Linked Server table & write it into the SQL Server local table.

In Object Explorer, connect to an instance of Database Engine and then expand that instance.

Expand Databases, expand your database, and then expand Programmability.

Right-click Stored Procedures and then click the New Stored Procedure.

We will create the stored procedure named Import_QODBC_Tables, which will check in the local database if the table exists. It will drop the table & recreate the table & read all the linked server tables & create a new table in a local database.

After writing the stored procedure, click on Execute to create the stored procedure.

Stored Procedure Created.

Stored Procedure Code:

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

USE [QODBC]
GO
/****** Object:  StoredProcedure [dbo].[Import_QODBC_Tables]    Script Date: 07/29/2016 00:28:38 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO


Create PROCEDURE [dbo].[Import_QODBC_Tables]


AS
begin

IF OBJECT_ID (N'Tbl_Account', N'U') IS NOT NULL
 
Drop table Tbl_Account
   
SELECT * INTO Tbl_Account    FROM QRemote...Account

IF OBJECT_ID (N'Tbl_AccountTaxLineInfo', N'U') IS NOT NULL
 
Drop table Tbl_AccountTaxLineInfo

SELECT * INTO    Tbl_AccountTaxLineInfo    FROM    QRemote...AccountTaxLineInfo

IF OBJECT_ID (N'Tbl_ARRefundCreditCard', N'U') IS NOT NULL
 
Drop table Tbl_ARRefundCreditCard

SELECT * INTO    Tbl_ARRefundCreditCard    FROM    QRemote...ARRefundCreditCard

IF OBJECT_ID (N'Tbl_ARRefundCreditCardRefundAppliedTo', N'U') IS NOT NULL
 
Drop table Tbl_ARRefundCreditCardRefundAppliedTo

SELECT * INTO    Tbl_ARRefundCreditCardRefundAppliedTo    FROM    QRemote...ARRefundCreditCardRefundAppliedTo

IF OBJECT_ID (N'Tbl_BarCode', N'U') IS NOT NULL
 
Drop table Tbl_BarCode

SELECT * INTO    Tbl_BarCode    FROM    QRemote...BarCode

IF OBJECT_ID (N'Tbl_Bill', N'U') IS NOT NULL
 
Drop table Tbl_Bill

SELECT * INTO    Tbl_Bill    FROM    QRemote...Bill

IF OBJECT_ID (N'Tbl_BillExpenseLine', N'U') IS NOT NULL
 
Drop table Tbl_BillExpenseLine

SELECT * INTO    Tbl_BillExpenseLine    FROM    QRemote...BillExpenseLine

IF OBJECT_ID (N'Tbl_BillItemLine', N'U') IS NOT NULL
 
Drop table Tbl_BillItemLine

SELECT * INTO    Tbl_BillItemLine    FROM    QRemote...BillItemLine

IF OBJECT_ID (N'Tbl_BillLinkedTxn', N'U') IS NOT NULL
 
Drop table Tbl_BillLinkedTxn

SELECT * INTO    Tbl_BillLinkedTxn    FROM    QRemote...BillLinkedTxn

IF OBJECT_ID (N'Tbl_BillingRate', N'U') IS NOT NULL
 
Drop table Tbl_BillingRate

SELECT * INTO    Tbl_BillingRate    FROM    QRemote...BillingRate

IF OBJECT_ID (N'Tbl_BillingRateLine', N'U') IS NOT NULL
 
Drop table Tbl_BillingRateLine

SELECT * INTO    Tbl_BillingRateLine    FROM    QRemote...BillingRateLine

IF OBJECT_ID (N'Tbl_BillPaymentCheck', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCheck

SELECT * INTO    Tbl_BillPaymentCheck    FROM    QRemote...BillPaymentCheck

IF OBJECT_ID (N'Tbl_BillPaymentCheckLine', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCheckLine

SELECT * INTO    Tbl_BillPaymentCheckLine    FROM    QRemote...BillPaymentCheckLine

IF OBJECT_ID (N'Tbl_BillPaymentCheckLineLinkedTxn', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCheckLineLinkedTxn

SELECT * INTO    Tbl_BillPaymentCheckLineLinkedTxn    FROM    QRemote...BillPaymentCheckLineLinkedTxn

IF OBJECT_ID (N'Tbl_BillPaymentCreditCard', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCreditCard

SELECT * INTO    Tbl_BillPaymentCreditCard    FROM    QRemote...BillPaymentCreditCard

IF OBJECT_ID (N'Tbl_BillPaymentCreditCardLine', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCreditCardLine

SELECT * INTO    Tbl_BillPaymentCreditCardLine    FROM    QRemote...BillPaymentCreditCardLine

IF OBJECT_ID (N'Tbl_BillPaymentCreditCardLineLinkedTxn', N'U') IS NOT NULL
 
Drop table Tbl_BillPaymentCreditCardLineLinkedTxn

SELECT * INTO    Tbl_BillPaymentCreditCardLineLinkedTxn    FROM    QRemote...BillPaymentCreditCardLineLinkedTxn

IF OBJECT_ID (N'Tbl_BillToPay', N'U') IS NOT NULL
 
Drop table Tbl_BillToPay

SELECT * INTO    Tbl_BillToPay    FROM    QRemote...BillToPay

IF OBJECT_ID (N'Tbl_BuildAssembly', N'U') IS NOT NULL
 
Drop table Tbl_BuildAssembly

SELECT * INTO    Tbl_BuildAssembly    FROM    QRemote...BuildAssembly

IF OBJECT_ID (N'Tbl_BuildAssemblyComponentItemLine', N'U') IS NOT NULL
 
Drop table Tbl_BuildAssemblyComponentItemLine

SELECT * INTO    Tbl_BuildAssemblyComponentItemLine    FROM    QRemote...BuildAssemblyComponentItemLine

IF OBJECT_ID (N'Tbl_Charge', N'U') IS NOT NULL
 
Drop table Tbl_Charge

SELECT * INTO    Tbl_Charge    FROM    QRemote...Charge

IF OBJECT_ID (N'Tbl_ChargeLinkedTxn', N'U') IS NOT NULL
 
Drop table Tbl_ChargeLinkedTxn

SELECT * INTO    Tbl_ChargeLinkedTxn    FROM    QRemote...ChargeLinkedTxn

IF OBJECT_ID (N'Tbl_Check', N'U') IS NOT NULL
 
Drop table Tbl_Check

SELECT * INTO    Tbl_Check    FROM    QRemote..."Check"

IF OBJECT_ID (N'Tbl_CheckApplyCheckToTxn', N'U') IS NOT NULL
 
Drop table Tbl_CheckApplyCheckToTxn

SELECT * INTO    Tbl_CheckApplyCheckToTxn    FROM    QRemote...CheckApplyCheckToTxn

IF OBJECT_ID (N'Tbl_CheckExpenseLine', N'U') IS NOT NULL
 
Drop table Tbl_CheckExpenseLine

SELECT * INTO    Tbl_CheckExpenseLine    FROM    QRemote...CheckExpenseLine

IF OBJECT_ID (N'Tbl_CheckItemLine', N'U') IS NOT NULL
 
Drop table Tbl_CheckItemLine

SELECT * INTO    Tbl_CheckItemLine    FROM    QRemote...CheckItemLine

IF OBJECT_ID (N'Tbl_Class', N'U') IS NOT NULL
 
Drop table Tbl_Class

SELECT * INTO    Tbl_Class    FROM    QRemote...Class

IF OBJECT_ID (N'Tbl_ClearedStatus', N'U') IS NOT NULL
 
Drop table Tbl_ClearedStatus

SELECT * INTO    Tbl_ClearedStatus    FROM    QRemote...ClearedStatus

IF OBJECT_ID (N'Tbl_Company', N'U') IS NOT NULL
 
Drop table Tbl_Company

SELECT * INTO    Tbl_Company    FROM    QRemote...Company

IF OBJECT_ID (N'Tbl_CompanyActivity', N'U') IS NOT NULL
 
Drop table Tbl_CompanyActivity

SELECT * INTO    Tbl_CompanyActivity    FROM    QRemote...CompanyActivity

IF OBJECT_ID (N'Tbl_CreditCardCharge', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardCharge

SELECT * INTO    Tbl_CreditCardCharge    FROM    QRemote...CreditCardCharge

IF OBJECT_ID (N'Tbl_CreditCardChargeExpenseLine', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardChargeExpenseLine

SELECT * INTO    Tbl_CreditCardChargeExpenseLine    FROM    QRemote...CreditCardChargeExpenseLine

IF OBJECT_ID (N'Tbl_CreditCardChargeItemLine', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardChargeItemLine

SELECT * INTO    Tbl_CreditCardChargeItemLine    FROM    QRemote...CreditCardChargeItemLine

IF OBJECT_ID (N'Tbl_CreditCardCredit', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardCredit

SELECT * INTO    Tbl_CreditCardCredit    FROM    QRemote...CreditCardCredit

IF OBJECT_ID (N'Tbl_CreditCardCreditExpenseLine', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardCreditExpenseLine

SELECT * INTO    Tbl_CreditCardCreditExpenseLine    FROM    QRemote...CreditCardCreditExpenseLine

IF OBJECT_ID (N'Tbl_CreditCardCreditItemLine', N'U') IS NOT NULL
 
Drop table Tbl_CreditCardCreditItemLine

SELECT * INTO    Tbl_CreditCardCreditItemLine    FROM    QRemote...CreditCardCreditItemLine

IF OBJECT_ID (N'Tbl_CreditMemo', N'U') IS NOT NULL
 
Drop table Tbl_CreditMemo

SELECT * INTO    Tbl_CreditMemo    FROM    QRemote...CreditMemo

IF OBJECT_ID (N'Tbl_CreditMemoLine', N'U') IS NOT NULL
 
Drop table Tbl_CreditMemoLine

SELECT * INTO    Tbl_CreditMemoLine    FROM    QRemote...CreditMemoLine

IF OBJECT_ID (N'Tbl_CreditMemoLinkedTxn', N'U') IS NOT NULL
 
Drop table Tbl_CreditMemoLinkedTxn

SELECT * INTO    Tbl_CreditMemoLinkedTxn    FROM    QRemote...CreditMemoLinkedTxn

IF OBJECT_ID (N'Tbl_Currency', N'U') IS NOT NULL
 
Drop table Tbl_Currency

SELECT * INTO    Tbl_Currency    FROM    QRemote...Currency

IF OBJECT_ID (N'Tbl_Customer', N'U') IS NOT NULL
 
Drop table Tbl_Customer

SELECT * INTO    Tbl_Customer    FROM    QRemote...Customer

IF OBJECT_ID (N'Tbl_CustomerAddtionalNote', N'U') IS NOT NULL
 
Drop table Tbl_CustomerAddtionalNote

SELECT * INTO    Tbl_CustomerAddtionalNote    FROM    QRemote...CustomerAddtionalNote

IF OBJECT_ID (N'Tbl_CustomerContacts', N'U') IS NOT NULL
 
Drop table Tbl_CustomerContacts

SELECT * INTO    Tbl_CustomerContacts    FROM    QRemote...CustomerContacts

IF OBJECT_ID (N'Tbl_CustomerShipToAddress', N'U') IS NOT NULL
 
Drop table Tbl_CustomerShipToAddress

SELECT * INTO    Tbl_CustomerShipToAddress    FROM    QRemote...CustomerShipToAddress

IF OBJECT_ID (N'Tbl_CustomerMsg', N'U') IS NOT NULL
 
Drop table Tbl_CustomerMsg

SELECT * INTO    Tbl_CustomerMsg    FROM    QRemote...CustomerMsg

IF OBJECT_ID (N'Tbl_CustomerType', N'U') IS NOT NULL
 
Drop table Tbl_CustomerType

SELECT * INTO    Tbl_CustomerType    FROM    QRemote...CustomerType

IF OBJECT_ID (N'Tbl_CustomField', N'U') IS NOT NULL
 
Drop table Tbl_CustomField

SELECT * INTO    Tbl_CustomField    FROM    QRemote...CustomField

IF OBJECT_ID (N'Tbl_DateDrivenTerms', N'U') IS NOT NULL
 
Drop table Tbl_DateDrivenTerms

SELECT * INTO    Tbl_DateDrivenTerms    FROM    QRemote...DateDrivenTerms

IF OBJECT_ID (N'Tbl_Deposit', N'U') IS NOT NULL
 
Drop table Tbl_Deposit

SELECT * INTO    Tbl_Deposit    FROM    QRemote...Deposit

IF OBJECT_ID (N'Tbl_DepositLine', N'U') IS NOT NULL
 
Drop table Tbl_DepositLine

SELECT * INTO    Tbl_DepositLine    FROM    QRemote...DepositLine

IF OBJECT_ID (N'Tbl_Employee', N'U') IS NOT NULL
 
Drop table Tbl_Employee

SELECT * INTO    Tbl_Employee    FROM    QRemote...Employee

IF OBJECT_ID (N'Tbl_EmployeeAddtionalNote', N'U') IS NOT NULL
 
Drop table Tbl_EmployeeAddtionalNote

SELECT * INTO    Tbl_EmployeeAddtionalNote    FROM    QRemote...EmployeeAddtionalNote

IF OBJECT_ID (N'Tbl_EmployeeEarning', N'U') IS NOT NULL
 
Drop table Tbl_EmployeeEarning

SELECT * INTO    Tbl_EmployeeEarning    FROM    QRemote...EmployeeEarning

IF OBJECT_ID (N'Tbl_Entity', N'U') IS NOT NULL
 
Drop table Tbl_Entity

SELECT * INTO    Tbl_Entity    FROM    QRemote...Entity

IF OBJECT_ID (N'Tbl_EntityAdditionalNote', N'U') IS NOT NULL
 
Drop table Tbl_EntityAdditionalNote

SELECT * INTO    Tbl_EntityAdditionalNote    FROM    QRemote...EntityAdditionalNote

IF OBJECT_ID (N'Tbl_EntityContacts', N'U') IS NOT NULL
 
Drop table Tbl_EntityContacts

SELECT * INTO    Tbl_EntityContacts    FROM    QRemote...EntityContacts

IF OBJECT_ID (N'Tbl_EntityShipToAddress', N'U') IS NOT NULL
 
Drop table Tbl_EntityShipToAddress

SELECT * INTO    Tbl_EntityShipToAddress    FROM    QRemote...EntityShipToAddress

IF OBJECT_ID (N'Tbl_Estimate', N'U') IS NOT NULL
 
Drop table Tbl_Estimate

SELECT * INTO    Tbl_Estimate    FROM    QRemote...Estimate

IF OBJECT_ID (N'Tbl_EstimateLine', N'U') IS NOT NULL
 
Drop table Tbl_EstimateLine

SELECT * INTO    Tbl_EstimateLine    FROM    QRemote...EstimateLine

IF OBJECT_ID (N'Tbl_EstimateLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_EstimateLinkedTxn
SELECT * INTO    Tbl_EstimateLinkedTxn    FROM    QRemote...EstimateLinkedTxn

IF OBJECT_ID (N'Tbl_Host', N'U') IS NOT NULL
Drop table Tbl_Host
SELECT * INTO    Tbl_Host    FROM    QRemote...Host

IF OBJECT_ID (N'Tbl_HostMetaData', N'U') IS NOT NULL
Drop table Tbl_HostMetaData
SELECT * INTO    Tbl_HostMetaData    FROM    QRemote...HostMetaData

IF OBJECT_ID (N'Tbl_HostSupportedVersions', N'U') IS NOT NULL
Drop table Tbl_HostSupportedVersions
SELECT * INTO    Tbl_HostSupportedVersions    FROM    QRemote...HostSupportedVersions

IF OBJECT_ID (N'Tbl_InventoryAdjustment', N'U') IS NOT NULL
Drop table Tbl_InventoryAdjustment
SELECT * INTO    Tbl_InventoryAdjustment    FROM    QRemote...InventoryAdjustment

IF OBJECT_ID (N'Tbl_InventoryAdjustmentLine', N'U') IS NOT NULL
Drop table Tbl_InventoryAdjustmentLine
SELECT * INTO    Tbl_InventoryAdjustmentLine    FROM    QRemote...InventoryAdjustmentLine

IF OBJECT_ID (N'Tbl_InventorySite', N'U') IS NOT NULL
Drop table Tbl_InventorySite
SELECT * INTO    Tbl_InventorySite    FROM    QRemote...InventorySite

IF OBJECT_ID (N'Tbl_Invoice', N'U') IS NOT NULL
Drop table Tbl_Invoice
SELECT * INTO    Tbl_Invoice    FROM    QRemote...Invoice

IF OBJECT_ID (N'Tbl_InvoiceLine', N'U') IS NOT NULL
Drop table Tbl_InvoiceLine
SELECT * INTO    Tbl_InvoiceLine    FROM    QRemote...InvoiceLine

IF OBJECT_ID (N'Tbl_InvoiceLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_InvoiceLinkedTxn
SELECT * INTO    Tbl_InvoiceLinkedTxn    FROM    QRemote...InvoiceLinkedTxn

IF OBJECT_ID (N'Tbl_Item', N'U') IS NOT NULL
Drop table Tbl_Item
SELECT * INTO    Tbl_Item    FROM    QRemote...Item

IF OBJECT_ID (N'Tbl_ItemAssembliesCanBuild', N'U') IS NOT NULL
Drop table Tbl_ItemAssembliesCanBuild
SELECT * INTO    Tbl_ItemAssembliesCanBuild    FROM    QRemote...ItemAssembliesCanBuild where ItemInventoryAssemblyRefFullName='assembly item' and TxnDate={d'2018-01-01'}

IF OBJECT_ID (N'Tbl_ItemDiscount', N'U') IS NOT NULL
Drop table Tbl_ItemDiscount
SELECT * INTO    Tbl_ItemDiscount    FROM    QRemote...ItemDiscount

IF OBJECT_ID (N'Tbl_ItemFixedAsset', N'U') IS NOT NULL
Drop table Tbl_ItemFixedAsset
SELECT * INTO    Tbl_ItemFixedAsset    FROM    QRemote...ItemFixedAsset

IF OBJECT_ID (N'Tbl_ItemGroup', N'U') IS NOT NULL
Drop table Tbl_ItemGroup
SELECT * INTO    Tbl_ItemGroup    FROM    QRemote...ItemGroup

IF OBJECT_ID (N'Tbl_ItemGroupLine', N'U') IS NOT NULL
Drop table Tbl_ItemGroupLine
SELECT * INTO    Tbl_ItemGroupLine    FROM    QRemote...ItemGroupLine

IF OBJECT_ID (N'Tbl_ItemInventory', N'U') IS NOT NULL
Drop table Tbl_ItemInventory
SELECT * INTO    Tbl_ItemInventory    FROM    QRemote...ItemInventory

IF OBJECT_ID (N'Tbl_ItemInventoryAssembly', N'U') IS NOT NULL
Drop table Tbl_ItemInventoryAssembly
SELECT * INTO    Tbl_ItemInventoryAssembly    FROM    QRemote...ItemInventoryAssembly

IF OBJECT_ID (N'Tbl_ItemInventoryAssemblyLine', N'U') IS NOT NULL
Drop table Tbl_ItemInventoryAssemblyLine
SELECT * INTO    Tbl_ItemInventoryAssemblyLine    FROM    QRemote...ItemInventoryAssemblyLine

IF OBJECT_ID (N'Tbl_ItemNonInventory', N'U') IS NOT NULL
Drop table Tbl_ItemNonInventory
SELECT * INTO    Tbl_ItemNonInventory    FROM    QRemote...ItemNonInventory

IF OBJECT_ID (N'Tbl_ItemOtherCharge', N'U') IS NOT NULL
Drop table Tbl_ItemOtherCharge
SELECT * INTO    Tbl_ItemOtherCharge    FROM    QRemote...ItemOtherCharge

IF OBJECT_ID (N'Tbl_ItemPayment', N'U') IS NOT NULL
Drop table Tbl_ItemPayment
SELECT * INTO    Tbl_ItemPayment    FROM    QRemote...ItemPayment

IF OBJECT_ID (N'Tbl_ItemReceipt', N'U') IS NOT NULL
Drop table Tbl_ItemReceipt
SELECT * INTO    Tbl_ItemReceipt    FROM    QRemote...ItemReceipt

IF OBJECT_ID (N'Tbl_ItemReceiptExpenseLine', N'U') IS NOT NULL
Drop table Tbl_ItemReceiptExpenseLine
SELECT * INTO    Tbl_ItemReceiptExpenseLine    FROM    QRemote...ItemReceiptExpenseLine

IF OBJECT_ID (N'Tbl_ItemReceiptItemLine', N'U') IS NOT NULL
Drop table Tbl_ItemReceiptItemLine
SELECT * INTO    Tbl_ItemReceiptItemLine    FROM    QRemote...ItemReceiptItemLine

IF OBJECT_ID (N'Tbl_ItemReceiptLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_ItemReceiptLinkedTxn
SELECT * INTO    Tbl_ItemReceiptLinkedTxn    FROM    QRemote...ItemReceiptLinkedTxn

IF OBJECT_ID (N'Tbl_ItemSalesTax', N'U') IS NOT NULL
Drop table Tbl_ItemSalesTax
SELECT * INTO    Tbl_ItemSalesTax    FROM    QRemote...ItemSalesTax

IF OBJECT_ID (N'Tbl_ItemSalesTaxGroup', N'U') IS NOT NULL
Drop table Tbl_ItemSalesTaxGroup
SELECT * INTO    Tbl_ItemSalesTaxGroup    FROM    QRemote...ItemSalesTaxGroup

IF OBJECT_ID (N'Tbl_ItemSalesTaxGroupLine', N'U') IS NOT NULL
Drop table Tbl_ItemSalesTaxGroupLine
SELECT * INTO    Tbl_ItemSalesTaxGroupLine    FROM    QRemote...ItemSalesTaxGroupLine

IF OBJECT_ID (N'Tbl_ItemSites', N'U') IS NOT NULL
Drop table Tbl_ItemSites
SELECT * INTO    Tbl_ItemSites    FROM    QRemote...ItemSites

IF OBJECT_ID (N'Tbl_ItemService', N'U') IS NOT NULL
Drop table Tbl_ItemService
SELECT * INTO    Tbl_ItemService    FROM    QRemote...ItemService

IF OBJECT_ID (N'Tbl_ItemSubtotal', N'U') IS NOT NULL
Drop table Tbl_ItemSubtotal
SELECT * INTO    Tbl_ItemSubtotal    FROM    QRemote...ItemSubtotal

IF OBJECT_ID (N'Tbl_JobType', N'U') IS NOT NULL
Drop table Tbl_JobType
SELECT * INTO    Tbl_JobType    FROM    QRemote...job type

IF OBJECT_ID (N'Tbl_JournalEntry', N'U') IS NOT NULL
Drop table Tbl_JournalEntry
SELECT * INTO    Tbl_JournalEntry    FROM    QRemote...JournalEntry

IF OBJECT_ID (N'Tbl_JournalEntryCreditLine', N'U') IS NOT NULL
Drop table Tbl_JournalEntryCreditLine
SELECT * INTO    Tbl_JournalEntryCreditLine    FROM    QRemote...JournalEntryCreditLine

IF OBJECT_ID (N'Tbl_JournalEntryDebitLine', N'U') IS NOT NULL
Drop table Tbl_JournalEntryDebitLine
SELECT * INTO    Tbl_JournalEntryDebitLine    FROM    QRemote...JournalEntryDebitLine

IF OBJECT_ID (N'Tbl_JournalEntryLine', N'U') IS NOT NULL
Drop table Tbl_JournalEntryLine
SELECT * INTO    Tbl_JournalEntryLine    FROM    QRemote...JournalEntryLine

IF OBJECT_ID (N'Tbl_ListDeleted', N'U') IS NOT NULL
Drop table Tbl_ListDeleted
SELECT * INTO    Tbl_ListDeleted    FROM    QRemote...ListDeleted

IF OBJECT_ID (N'Tbl_OtherName', N'U') IS NOT NULL
Drop table Tbl_OtherName
SELECT * INTO    Tbl_OtherName    FROM    QRemote... another name

IF OBJECT_ID (N'Tbl_PaymentMethod', N'U') IS NOT NULL
Drop table Tbl_PaymentMethod
SELECT * INTO    Tbl_PaymentMethod    FROM    QRemote...payment method

IF OBJECT_ID (N'Tbl_PayrollItemNonWage', N'U') IS NOT NULL
Drop table Tbl_PayrollItemNonWage
SELECT * INTO    Tbl_PayrollItemNonWage    FROM    QRemote...PayrollItemNonWage

IF OBJECT_ID (N'Tbl_PayrollItemWage', N'U') IS NOT NULL
Drop table Tbl_PayrollItemWage
SELECT * INTO    Tbl_PayrollItemWage    FROM    QRemote...PayrollItemWage

IF OBJECT_ID (N'Tbl_Preferences', N'U') IS NOT NULL
Drop table Tbl_Preferences
SELECT * INTO    Tbl_Preferences    FROM    QRemote...Preferences

IF OBJECT_ID (N'Tbl_PriceLevel', N'U') IS NOT NULL
Drop table Tbl_PriceLevel
SELECT * INTO    Tbl_PriceLevel    FROM    QRemote...PriceLevel

IF OBJECT_ID (N'Tbl_PriceLevelPerItem', N'U') IS NOT NULL
Drop table Tbl_PriceLevelPerItem
SELECT * INTO    Tbl_PriceLevelPerItem    FROM    QRemote...PriceLevelPerItem

IF OBJECT_ID (N'Tbl_PurchaseOrder', N'U') IS NOT NULL
Drop table Tbl_PurchaseOrder
SELECT * INTO    Tbl_PurchaseOrder    FROM    QRemote...PurchaseOrder

IF OBJECT_ID (N'Tbl_PurchaseOrderLine', N'U') IS NOT NULL
Drop table Tbl_PurchaseOrderLine
SELECT * INTO    Tbl_PurchaseOrderLine    FROM    QRemote...PurchaseOrderLine

IF OBJECT_ID (N'Tbl_PurchaseOrderLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_PurchaseOrderLinkedTxn
SELECT * INTO    Tbl_PurchaseOrderLinkedTxn    FROM    QRemote...PurchaseOrderLinkedTxn

IF OBJECT_ID (N'Tbl_ReceivePayment', N'U') IS NOT NULL
Drop table Tbl_ReceivePayment
SELECT * INTO    Tbl_ReceivePayment    FROM    QRemote...receive payment

IF OBJECT_ID (N'Tbl_ReceivePaymentLine', N'U') IS NOT NULL
Drop table Tbl_ReceivePaymentLine
SELECT * INTO    Tbl_ReceivePaymentLine    FROM    QRemote...ReceivePaymentLine

IF OBJECT_ID (N'Tbl_ReceivePaymentLineLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_ReceivePaymentLineLinkedTxn
SELECT * INTO    Tbl_ReceivePaymentLineLinkedTxn    FROM    QRemote...ReceivePaymentLineLinkedTxn

IF OBJECT_ID (N'Tbl_ReceivePaymentToDeposit', N'U') IS NOT NULL
Drop table Tbl_ReceivePaymentToDeposit
SELECT * INTO    Tbl_ReceivePaymentToDeposit    FROM    QRemote...ReceivePaymentToDeposit

IF OBJECT_ID (N'Tbl_Sales', N'U') IS NOT NULL
Drop table Tbl_Sales
SELECT * INTO    Tbl_Sales    FROM    QRemote...Sales

IF OBJECT_ID (N'Tbl_SalesLine', N'U') IS NOT NULL
Drop table Tbl_SalesLine
SELECT * INTO    Tbl_SalesLine    FROM    QRemote...SalesLine

IF OBJECT_ID (N'Tbl_SalesOrder', N'U') IS NOT NULL
Drop table Tbl_SalesOrder
SELECT * INTO    Tbl_SalesOrder    FROM    QRemote...SalesOrder

IF OBJECT_ID (N'Tbl_SalesOrderLine', N'U') IS NOT NULL
Drop table Tbl_SalesOrderLine
SELECT * INTO    Tbl_SalesOrderLine    FROM    QRemote...SalesOrderLine

IF OBJECT_ID (N'Tbl_SalesOrderLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_SalesOrderLinkedTxn
SELECT * INTO    Tbl_SalesOrderLinkedTxn    FROM    QRemote...SalesOrderLinkedTxn

IF OBJECT_ID (N'Tbl_SalesReceipt', N'U') IS NOT NULL
Drop table Tbl_SalesReceipt
SELECT * INTO    Tbl_SalesReceipt    FROM    QRemote...SalesReceipt

IF OBJECT_ID (N'Tbl_SalesReceiptLine', N'U') IS NOT NULL
Drop table Tbl_SalesReceiptLine
SELECT * INTO    Tbl_SalesReceiptLine    FROM    QRemote...SalesReceiptLine

IF OBJECT_ID (N'Tbl_SalesRep', N'U') IS NOT NULL
Drop table Tbl_SalesRep
SELECT * INTO    Tbl_SalesRep    FROM    QRemote...SalesRep

IF OBJECT_ID (N'Tbl_SalesTaxCode', N'U') IS NOT NULL
Drop table Tbl_SalesTaxCode
SELECT * INTO    Tbl_SalesTaxCode    FROM    QRemote...SalesTaxCode

IF OBJECT_ID (N'Tbl_SalesTaxPaymentCheck', N'U') IS NOT NULL
Drop table Tbl_SalesTaxPaymentCheck
SELECT * INTO    Tbl_SalesTaxPaymentCheck    FROM    QRemote...SalesTaxPaymentCheck

IF OBJECT_ID (N'Tbl_SalesTaxPaymentCheckLine', N'U') IS NOT NULL
Drop table Tbl_SalesTaxPaymentCheckLine
SELECT * INTO    Tbl_SalesTaxPaymentCheckLine    FROM    QRemote...SalesTaxPaymentCheckLine

IF OBJECT_ID (N'Tbl_ShipMethod', N'U') IS NOT NULL
Drop table Tbl_ShipMethod
SELECT * INTO    Tbl_ShipMethod    FROM    QRemote...ShipMethod

IF OBJECT_ID (N'Tbl_SpecialAccount', N'U') IS NOT NULL
Drop table Tbl_SpecialAccount
SELECT * INTO    Tbl_SpecialAccount    FROM    QRemote...SpecialAccount

IF OBJECT_ID (N'Tbl_SpecialItem', N'U') IS NOT NULL
Drop table Tbl_SpecialItem
SELECT * INTO    Tbl_SpecialItem    FROM    QRemote...SpecialItem

IF OBJECT_ID (N'Tbl_StandardTerms', N'U') IS NOT NULL
Drop table Tbl_StandardTerms
SELECT * INTO    Tbl_StandardTerms    FROM    QRemote...StandardTerms

IF OBJECT_ID (N'Tbl_TaxCode', N'U') IS NOT NULL
Drop table Tbl_TaxCode
SELECT * INTO    Tbl_TaxCode    FROM    QRemote...TaxCode

IF OBJECT_ID (N'Tbl_Template', N'U') IS NOT NULL
Drop table Tbl_Template
SELECT * INTO    Tbl_Template    FROM    QRemote...Template

IF OBJECT_ID (N'Tbl_Terms', N'U') IS NOT NULL
Drop table Tbl_Terms
SELECT * INTO    Tbl_Terms    FROM    QRemote...Terms

IF OBJECT_ID (N'Tbl_TimeTracking', N'U') IS NOT NULL
Drop table Tbl_TimeTracking
SELECT * INTO    Tbl_TimeTracking    FROM    QRemote...TimeTracking

IF OBJECT_ID (N'Tbl_ToDo', N'U') IS NOT NULL
Drop table Tbl_ToDo
SELECT * INTO    Tbl_ToDo    FROM    QRemote...ToDo

IF OBJECT_ID (N'Tbl_Transaction', N'U') IS NOT NULL
Drop table Tbl_Transaction
SELECT * INTO    Tbl_Transaction    FROM    QRemote..."Transaction"

IF OBJECT_ID (N'Tbl_Transfer', N'U') IS NOT NULL
Drop table Tbl_Transfer
SELECT * INTO    Tbl_Transfer    FROM    QRemote...Transfer

IF OBJECT_ID (N'Tbl_TransferInventory', N'U') IS NOT NULL
Drop table Tbl_TransferInventory
SELECT * INTO    Tbl_TransferInventory    FROM    QRemote...TransferInventory

IF OBJECT_ID (N'Tbl_TransferInventoryLine', N'U') IS NOT NULL
Drop table Tbl_TransferInventoryLine
SELECT * INTO    Tbl_TransferInventoryLine    FROM    QRemote...TransferInventoryLine

IF OBJECT_ID (N'Tbl_TxnDeleted', N'U') IS NOT NULL
Drop table Tbl_TxnDeleted
SELECT * INTO    Tbl_TxnDeleted    FROM    QRemote...TxnDeleted

IF OBJECT_ID (N'Tbl_UnitOfMeasureSet', N'U') IS NOT NULL
Drop table Tbl_UnitOfMeasureSet
SELECT * INTO    Tbl_UnitOfMeasureSet    FROM    QRemote...UnitOfMeasureSet

IF OBJECT_ID (N'Tbl_UnitOfMeasureSetRelatedUnit', N'U') IS NOT NULL
Drop table Tbl_UnitOfMeasureSetRelatedUnit
SELECT * INTO    Tbl_UnitOfMeasureSetRelatedUnit    FROM    QRemote...UnitOfMeasureSetRelatedUnit

IF OBJECT_ID (N'Tbl_UnitOfMeasureSetDefaultUnit', N'U') IS NOT NULL
Drop table Tbl_UnitOfMeasureSetDefaultUnit
SELECT * INTO    Tbl_UnitOfMeasureSetDefaultUnit    FROM    QRemote...UnitOfMeasureSetDefaultUnit

IF OBJECT_ID (N'Tbl_Vehicle', N'U') IS NOT NULL
Drop table Tbl_Vehicle
SELECT * INTO    Tbl_Vehicle    FROM    QRemote...Vehicle

IF OBJECT_ID (N'Tbl_VehicleMileage', N'U') IS NOT NULL
Drop table Tbl_VehicleMileage
SELECT * INTO    Tbl_VehicleMileage    FROM    QRemote...VehicleMileage

IF OBJECT_ID (N'Tbl_Vendor', N'U') IS NOT NULL
Drop table Tbl_Vendor
SELECT * INTO    Tbl_Vendor    FROM    QRemote...Vendor

IF OBJECT_ID (N'Tbl_VendorContacts', N'U') IS NOT NULL
Drop table Tbl_VendorContacts
SELECT * INTO    Tbl_VendorContacts    FROM    QRemote...VendorContacts

IF OBJECT_ID (N'Tbl_VendorCredit', N'U') IS NOT NULL
Drop table Tbl_VendorCredit
SELECT * INTO    Tbl_VendorCredit    FROM    QRemote...VendorCredit

IF OBJECT_ID (N'Tbl_VendorCreditExpenseLine', N'U') IS NOT NULL
Drop table Tbl_VendorCreditExpenseLine
SELECT * INTO    Tbl_VendorCreditExpenseLine    FROM    QRemote...VendorCreditExpenseLine

IF OBJECT_ID (N'Tbl_VendorCreditItemLine', N'U') IS NOT NULL
Drop table Tbl_VendorCreditItemLine
SELECT * INTO    Tbl_VendorCreditItemLine    FROM    QRemote...VendorCreditItemLine

IF OBJECT_ID (N'Tbl_VendorCreditLinkedTxn', N'U') IS NOT NULL
Drop table Tbl_VendorCreditLinkedTxn
SELECT * INTO    Tbl_VendorCreditLinkedTxn    FROM    QRemote...VendorCreditLinkedTxn

IF OBJECT_ID (N'Tbl_VendorType', N'U') IS NOT NULL
Drop table Tbl_VendorType
SELECT * INTO    Tbl_VendorType    FROM    QRemote...VendorType

IF OBJECT_ID (N'Tbl_WorkersCompCode', N'U') IS NOT NULL
Drop table Tbl_WorkersCompCode
SELECT * INTO    Tbl_WorkersCompCode    FROM    QRemote...WorkersCompCode

IF OBJECT_ID (N'Tbl_WorkersCompCodeRateHistory', N'U') IS NOT NULL
Drop table Tbl_WorkersCompCodeRateHistory
SELECT * INTO    Tbl_WorkersCompCodeRateHistory    FROM    QRemote...WorkersCompCodeRateHistory

end

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

All tables are imported to the SQL Server Database by executing this stored procedure.

You can see that all tables are imported into the SQL Server Database.

You can add this stored procedure to SQL Agent & schedule it. So it will automatically add all tables to the SQL Server Database.

Now we will add this stored procedure to SQL Agent.

Right-click on SQL Server Agent & click on New >> Job to create a new Job.

A New Job pop-up will appear. Specify the name of the job.

Click next on the "Steps" in the left menu. An SQL job can contain one or more steps. A step might be simply an SQL statement or a stored procedure call. Add your effort here.

Enter the step name and type. Select the database, write the stored procedure execution command "exec Import_QODBC_Tables," & click ok.

Job step added.

The job is added to SQL Server Agent.

You can run a Job by right-clicking on the Job name & click on "Start Job at Step..."

The job is executing.

Download Sample

Before using the MS Excel application, please ensure you have installed the MS Office Component named "Microsoft Query." About MS Query, please refer to Microsoft Office with MS Query and QODBC for more.

It would be best if you opened QuickBooks & load the company file in QuickBooks.

Open MS Excel & create a new spreadsheet.
First, please select the "Data" tab, navigate to "From Other Sources"->" From Microsoft Query."

Note: In recent versions of Microsoft Excel (including Excel 365), the Microsoft Query (Legacy) feature is hidden by default from the Get Data tab.
Please refer to Troubleshooting - How to enable Microsoft Excel 365 - Legacy Microsoft Query

And then, in the "Choose Data Source" Window, please select a DSN to continue. (Here, I choose the default data source with a sample company file open. And check to use the Query Wizard to create/edit queries.

'QuickBooks Data' as an example:

The first time you used MS Excel to access QuickBooks. You will be asked to grant access permission for QODBC. After you grant permission for QODBC, you will be guided by the Query Wizard. Choose any table and click "Next" until you reach the Query Wizard.

Select View data or edit query in Microsoft Query & click Finish:

Write a query & click OK. In this example, I am writing a Trial Balance report query.
sp_report TrialBalance show Debit_Title, Credit_Title, Label, Debit, Credit parameters DateMacro = 'LastMonth', ReportBasis = 'Cash'

You will get the following message box about the SQL Query. Click OK.

Report data is available in Microsoft Query:

Click on File & Return Data to Microsoft Excel to save the export report in an Excel spreadsheet.

When you finish the query, choose to save it so that the next time you can directly use it. Leaving MS Query, MS Excel will ask you to import the query result into MS Excel:

Report Data is exported to an Excel spreadsheet.

Now we will disable auto-refresh of data from Data-->Connection-->Properties-->Uncheck Enable Background Refresh & Click OK:

Now we will add a button & we will write code for the button click event. On button click, it will open the connection, refresh the report data & close the connection.

You can add a button from the Developer tab in MS Excel. If the Developer tab is not available, display it.

Display the Developer tab.
Click the File tab, click Options, and then click the Customize Ribbon category.
Select the Developer check box in the Main Tabs list, and click OK.

On the Developer tab, in the Controls group, click Insert, and then under ActiveX Controls, click Command Button.

Command Button is added. I have renamed it to Refresh Data. Double-click on the command button to write code.

Write the code below to open the connection, refresh the report data & close the connection.

Private Sub CommandButton1_Click()
ActiveWorkbook.Connections("Query from QuickBooks Data"). Refresh
End Sub

Note: Query from QuickBooks Data is the name of the connection. You can get it from the Data--> Connections.

Report Data will be refreshed by clicking the Refresh Data button.

Problem Description:

I am trying to connect to QuickBooks Online using QODBC Online. However, I am encountering the error below at the time of connection.



Could you please help me resolve this error?

Solution:

QODBC Online is using the default port 8383. You will get the above error message when you have changed the port number in QODBC Online.

So, if you have changed the port number from the QODBC Online Setup Screen, then please close all the applications, wait for 5 to 10 minutes, and try to connect again.

If the above does not resolve the issue, then please ensure that no other application is using this port.

If any other application is not using the port specified on the QODBC Online Setup Screen, then you need to restart Windows & test again.

If any other application uses the port specified on the QODBC Online Setup Screen, you need to change the port from the QODBC Online Setup Screen.

You can change the port from:

Start >> All Programs >> QODBC Driver for use with QuickBooks Online >> Configure QODBC Online Data Source >> Go To "System DSN" Tab>> select QuickBooks Online Data >> click "configure" >> switch to General tab



Simply enter the port number you want to use in the "Port:" textbox and click "OK." In this example, I am changing it to the default port 8383.



After changing the port, please close all applications, wait for 5 to 10 minutes, and then try to connect again. If it does not work, you need to restart Windows & test again.

If you are still facing issues, then please raise a support ticket to the QODBC Technical Support department by clicking here

Tags: QuickBooks Online, QBO, QODBC Online, Port, Begin session, Unable to load component

Download Sample

There is a limitation with the QuickBooks Desktop SDK: it can connect only one company file to a user session at a time.

It means you cannot access multiple company files at the same time.

You need to close the connection with one company file and switch to another. ( i.e., connection closed for company A and Connection open for company B should have a gap of 15-30 seconds for switching operation.)

This applies to QuickBooks Desktop. When using QuickBooks Online, you can connect to multiple company files simultaneously.

In this article, we will connect to two different QuickBooks Desktop company files using two different QODBC DSNs with auto login configured. In this example, we will use two auto logins, DSN CompanyA & CompanyB.

Please Refer:
How to set up QODBC Desktop for Auto-login into QuickBooks Desktop
How to set up the QODBC Driver to auto-connect to QuickBooks Desktop. (Video)

Here is my DSN configuration for the First QuickBooks Desktop Company file.

It would be best if you opened QuickBooks Desktop & loaded the company file that you have chosen in the auto login DSN. The company file path in QuickBooks & DSN should be matched.

Open MS Excel & create a new spreadsheet.
First, please select the "Data" tab, navigate to "From Other Sources"->" From Microsoft Query."

Note: In recent versions of Microsoft Excel (including Excel 365), the Microsoft Query (Legacy) feature is hidden by default from the Get Data tab.

Please refer to Troubleshooting - How to enable Microsoft Excel 365 - Legacy Microsoft Query. 

And then, in the "Choose Data Source" Window, please select a DSN to continue. (Here, I choose the default data source with a sample company file open. And check to use the Query Wizard to create/edit queries.)

'CompanyA' as an example:

The first time you use MS Excel to access QuickBooks Desktop, you will be asked to grant access permission for QODBC. After you grant permission for QODBC, you will be guided by the Query Wizard. Choose any table and click "Next" until you reach the Query Wizard.

Select View data or edit query in Microsoft Query & click Finish:

Write a query & click OK. In this example, I am writing a Trial Balance report query.
sp_report TrialBalance show Debit_Title, Credit_Title, Label, Debit, Credit parameters DateMacro = 'LastMonth', ReportBasis = 'Cash'

You will get the following message box about the SQL Query. Click OK.

Report data is available in Microsoft Query:

Click on File & Return Data to Microsoft Excel to save the export report in an Excel spreadsheet.

When you finish the query, choose to save it so that the next time you can directly use it. Leaving MS Query, MS Excel will ask you to import the query result into MS Excel:

Report Data is exported to an Excel sheet.

Repeating the above steps will export another report in sheet 2 using DSN CompanyB.

We need to close the first company file, which is open in QuickBooks Desktop.

Here is my DSN configuration for the Second Company file.

It would be best if you opened QuickBooks Desktop and loaded the company file that you have chosen in the auto login DSN. The company file path in QuickBooks & DSN should be matched.

Navigate to sheet2
First, please select the "Data" tab, navigate to "From Other Sources"->" From Microsoft Query."

And then, in the "Choose Data Source" Window, please select a DSN to continue. (Here, I choose the default data source with a sample company file open. And check to use the Query Wizard to create/edit queries.)

'CompanyB' as an example:

The first time you use MS Excel to access QuickBooks Desktop, you will be asked to grant access permission for QODBC. After you grant permission for QODBC, you will be guided by the Query Wizard. Choose any table and click "Next" until you reach the Query Wizard.

Select View data or edit query in Microsoft Query & click Finish:

Write a query & click OK. In this example, I am writing a Profit & Loss report query.
sp_report ProfitAndLossStandard show Amount_Title, Text, Label, Amount parameters DateMacro = 'ThisMonthToDate', SummarizeColumnsBy = 'TotalOnly'

You will get the following message box about the SQL Query. Click OK.

Report data is available in Microsoft Query:

Click on File & Return Data to Microsoft Excel to save the export report in an Excel spreadsheet.

When you finish the query, choose to save it so that the next time you can directly use it. Leaving MS Query, MS Excel will ask you to import the query result into MS Excel:

Report Data is exported to an Excel sheet 2.

After the export is complete, close the company file opened in QuickBooks Desktop.

Now we will disable auto-refresh of data from Data-->Connection-->Properties-->Uncheck Enable Background Refresh & Click OK:

We need to disable auto-refresh data for both company file connections (i.e., Query from CompanyA & Query from CompanyB ).

Now we will add a button & we will write code for the button click event. On button click, it will open the connection for CompanyA, refresh the report data & close the connection for CompanyA, sleep for 15 seconds, open the connection for CompanyB, refresh the report data & close the connection for CompanyB.

You can add a button from the Developer tab in MS Excel. If the Developer tab is not available, display it.

Display the Developer tab.
Click the File tab, click Options, and then click the Customize Ribbon category.
Select the Developer check box in the Main Tabs list, and click OK.

On the Developer tab, in the Controls group, click Insert, and then under ActiveX Controls, click Command Button.

Command Button is added. I have renamed it to Refresh Data. Double-click on the command button to write code.

Write the code below to open a connection for Company A, refresh the report data & close the connection for Company A, sleep for 15 seconds, open the connection for CompanyB, restore the report data & close the connection for CompanyB.

Fifteen seconds of sleep are required to close the company file and switch to another private Sub CommandButton1_Click()
ActiveWorkbook.Connections("Query from CompanyA"). Refresh
Application.Wait (Now + TimeValue("0:00:15"))
ActiveWorkbook.Connections("Query from CompanyB").Refresh
End Sub

Report Data will be refreshed by clicking the Refresh Data button.

Keywords: QuickBooks Desktop, win log with multiple companies, log in with various companies

Problem Description:

I am getting an error SOCKET Closed because of an abnormal package in the QRemote client. I am accessing QuickBooks Data from the remote machine over the internet (WAN). 

Solution:

This issue will occur when the QRemote client & QRemote Server have different network types.The 

Windows component is internally checking the connection every 4 minutes. If there is no activity between the client & server, the Windows component will close the connection after 4 minutes & due to this, when the QRemote client tries to connect to the QRemote Server, it will not be able to connect, & SOCKET is Closed because an abnormal package error occurred.

To resolve this issue, you need to set the AutoClose value to 3 minutes for closing the broken connection in QRemote Server.

You can find the QRemote Server running in the System Tray. If QRemote Server is not running, then you can run it from Start >> All Programs >> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC.



Open QRemote Server. Go to File Menu -> Settings -> Advanced Tab. Set AutoClose broken connection after 3 minutes & apply the setting by clicking the Apply button.



After applying the settings. Please restart the QRemote Server & test again. To continue QRemote Server, go to File Menu -> Exit -> :

You will get a pop-up window with the message. Do you want to close the QRemote Server? Please click on OK to close QRemoteServer.

Please rerun QRemoteServer & test. You can QRemoteServer from:
Start >> All Programs >> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

Download Sample

ADODB with QODBC

Open VB6, you can find it via Windows Start->All Programs->Microsoft Visual Studio 6.0 :

Create a New Standard EXE project.

Then, add a "Command Button" by double-clicking on the command button Icon. A command button will be added. Rename it to Get Customer via ADODB:

Double click on the Command Button & add the code below in the Command Button click event:

Private Sub Command1_Click()

Dim oConnection As ADODB.Connection
Dim oRecordset As ADODB.Recordset
Dim sMsg As String
Dim sConnectString As String
Dim sSQL As String

sConnectString = "DSN=QuickBooks Data;OLE DB Services=-2;"
sSQL = "SELECT top 10 Name FROM Customer"
Set oConnection = New ADODB.Connection
Set oRecordset = New ADODB.Recordset
oConnection.Open sConnectString
oRecordset.Open sSQL, oConnection, adOpenStatic, adLockOptimistic
sMsg = "**********************" & Chr(10)
Do While (Not oRecordset.EOF)
sMsg = sMsg & oRecordset.Fields("Name") & Chr(10)
oRecordset.MoveNext
Loop
sMsg = sMsg & "**********************" & Chr(10)
MsgBox sMsg

oRecordset.Close
Set oRecordset = Nothing
oConnection.Close
Set oConnection = Nothing

End Sub

Now execute the code from Run >> Start With Full Compile

Double click on Get Customer via ADODB, which will get the top 10 customers' names & display them in msg box:

ADODC with QODBC

Now we will add an ADODC control in the same project we created in the above ADODB example.

Now we will configure ADODC control by right-clicking on the ADODC control & clicking on ADODC Properties:

From the General tab, select ODBC Data Source, QuickBooks Data.

Navigate to the RecordSource tab, select Command type to 2 - adCmdTable & table name Customer, and click OK.

Now we will add three text boxes showing the Customer table data through the ADODC control.

Now we will configure text boxes to display data from the ADODC control. Choose DataSource Adodc1 (i.e., ADODC Control name) & DataField FullName (i.e., Field name which you want to show):

Similarly, we will configure the other two textboxes with the Phone & Email fields.

Now execute the code from Run >> Start With Full Compile.

The following customer data will be displayed by clicking on the "Next" button.

Problem Description:

I am trying to export data from QXL. But when I clicked on the QXL export button, I got the following error message.

Unable to connect to QuickBooks. Popup window(s) in the QuickBooks application MUST be closed before QXL can communicate with QuickBooks.

Error Occurred: ERROR [00000] [QODBC] QuickBooks Begin Session Failed. Error = 80040414. A modal dialog box is showing in the QuickBooks user interface. Your application cannot access QuickBooks until the user dismisses the dialog box.

Solution:

Please navigate to QuickBooks & make sure that there is no modal pop-up window open in QuickBooks. If any modal pop-up window is available in QuickBooks, you will get an "Error = 80040414; A modal dialog box is showing in the QuickBooks user interface....". QuickBooks says that a modal connection is active for this part of QuickBooks, and you need to wait.

It would be best if you closed this modal popup window in QuickBooks & export data using QXL.

QXL does not have control over the modal pop-up window in QuickBooks. QXL cannot suppress or bypass this type of dialogue. It would be best if you disabled the modal pop-up from QuickBooks.

Tags: Unable to connect to QuickBooks using QXL

Problem Description:

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

How to cancel the subscription of the QODBC Driver for QuickBooks Online?

 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 Online 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 Online 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 Online subscription:

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

Intuit is reinforcing existing security features that help protect QuickBooks customers’ sensitive information.
Refer: Intuit's News: Changes to the Integrated Application Authentication for QuickBooks Desktop users


As a result of this effort, Intuit is delivering an update that impacts third-party applications that connect to QuickBooks using the QuickBooks SDK.

A new file specific to a Windows user on a given machine is created on user login that provides access to an SDK app in QuickBooks.

The implementation of this update will require customers to re-enter their login credentials & authorize the application(i.e., QODBC) at QuickBooks.

For Example, you have four Windows users. All four Windows users use QODBC via Microsoft Excel, Access, Crystal, or other applications. You will need to authorize EACH application from all 4 Windows users. That means you will need to log in to the 1st Windows user, endorse all the applications that will be using QODBC, then log in to the 2nd Windows user and authorize all the applications that will be using QODBC. This is because Intuit's LGB file, which was common earlier, has not changed to a new method, and integration information will be stored for each Windows user separately.

The above is applicable for a Single machine, Terminal Services(Remote desktop connection), or Workstation(s).

Problem Description:

Get the following errors from the QODBC driver:

ERROR [00000] [QODBC] QuickBooks Begin Session Failed. Error = 8004041d,80040418. This application cannot log into this QuickBooks company data file automatically. The QuickBooks administrator can grant permission for automatic login through the Integrated Application preferences.

Test connection to QuickBooks - FAILED: "[QODBC] QuickBooks Begin Session Failed. Error = 8004041a. This application does not have permission to access this QuickBooks company data file. The QuickBooks administrator can grant access permission through the Integrated Application preferences."

Solution 1:

Step 1: Launch QuickBooks and Open the Company File

Open QuickBooks Desktop.

Log in to the desired company file using the QuickBooks user "Admin".

Log in to the QuickBooks user "admin" is required to authorize the connection to the QuickBooks company file.

This is a one-time activity for each new application you want to connect to QuickBooks Data.

Step 2: Test connection using QODBC 32-Bit Test Tool

Go to Start → QODBC Driver for QuickBooks → QODBC 32-Bit Test Tool.

In the QODBC Test Tool, 

Select DSN: QuickBooks Data

Click the "Connect" button.

QuickBooks may prompt you to authorize access: (optional)

If prompted, choose “Yes, always; allow access even if QuickBooks is not running”.

Select the Admin user from the dropdown (if applicable).

Click Continue → Done.

If the connection is successful, you can optionally run a test query (e.g., SELECT * FROM Customer).

Click "Disconnect" to close the connection.

Step 3: Test connection using QODBC 64-Bit Test Tool

Go to Start → QODBC Driver for QuickBooks → QODBC 64-Bit Test Tool.

In the QODBC Test Tool, 

Select DSN: QuickBooks Data

Click the "Connect" button.

This should successfully establish a 64-bit connection. You may not be prompted for permission, as it has been granted in Step 2.

Once confirmed, click "OK" or "Disconnect" to close the session.

Step 4: Connect Using Your Application

In your application (e.g., PHP, .NET, Excel, Access, etc.), use the DSN name "QuickBooks Data" to establish a connection.

QuickBooks may prompt you to authorize access: (optional)

If QuickBooks does not ask for authorization, your application might already be authorized. You can run a few SQL statements/queries to verify that the connection is successful.

If you are unable to connect, please ensure you have logged in to the QuickBooks company file as the QuickBooks user "admin."

Solution 2:

You need to follow the steps below to reauthorize QODBC for QuickBooks.
1. Log in to Windows, Open QuickBooks & log in to the company file as Admin.
2. Switch Company File to Single User Mode.

3. Connect using your application. It should pop up the Data Access Certificate on QuickBooks. Please accept the Certificate. QuickBooks issues a Certificate for each application, so you need to get the Certificate for all applications that you use with QuickBooks.

4. You must log in to each Windows user accessing QuickBooks Data using QODBC.
If Windows User/Work Station changes, you must reauthorize the application using the above steps.

If the company file has Personally Identifiable Information (PII) in QuickBooks, users must log in with a password; the SDK app will only be allowed to connect once the login has been completed for that user. 

Customers will be instructed to set up a strong password when logging in. Customers should use unique letters and numbers in a password, not essential words that can easily be found online or in the dictionary.

Problem Description:

We downloaded the QODBC trial from your website. At the end of the installation process - after clicking the 'finish' button, a dialog appears saying that 'explorer.exe' cannot be found.

I am getting the following error:

Windows cannot find 'C:\Users\SAMMYH~1\WINDOWS\explorer.exe'. Make sure you typed the name correctly, and then try again.


Could not execute the external program

C:\Users\SAMMYH~1\WINDOWS\explorer.exe


The installation process aborts, and the software is then uninstalled.

Solution:

This issue occurs when using the QODBC V16.0.0.317 installer & Windows folder is personalized to point to the User's Roaming profile. We have fixed this issue in our latest version of QODBC (V318 or above). You can download the latest QODBC by clicking here.

If you want to use QODBC V317, then please follow the steps below to resolve the issue:

1. Open Windows Explorer.
Navigate to
C:\Windows\




2. Inside the "Windows" folder, you should find "explorer.exe."


Copy explorer.exe by right-clicking on explorer.exe & clicking copy.


3. Navigate to

C:\Users\Windows Username\Windows\
(Windows Username = The current logged-in Windows Username)

In this example, my Windows username is Dewani. So I am navigated to C:\Users\Dewani\Windows.


4. Paste the copied file in the directory C:\users\Windows Username\Windows\
In this example, my Windows username is Dewani. So I am pasting the file to C:\Users\Dewani\Windows. By right-clicking on the C:\Users\Dewani\Windows folder & clicking Paste.




5. Now try to install QODBC again. You will not get this error.

Either QODBC or QRemote is required on the machine where the SSIS package will be developed and deployed, or SSIS services are installed.

Development - On the machine where you are developing, the SSIS package should have QODBC installed.

Deployment - On the machine you wish to deploy or run the SSIS Package - You should have QODBC installed. 

The first step is to install and test QODBC.

Please refer to Connecting QODBC Driver to QuickBooks for the First Time (Video)

If the QuickBooks application is installed on another machine, you can connect to QuickBooks from a remote device using QRemote Server. You need to install QODBC on both machines.

Please refer to Accessing QuickBooks Data Remotely using QODBC & QRemote. (Video)

When deploying the SSIS package to SQL Server, you need to configure the QRemote client to connect with QuickBooks.

Please follow the steps below to use QODBC with SSIS.

1. Go to the Start menu & open SQL Server Business Intelligence Development Studio from SQL Server.

2. Create a new Integration Service Project by clicking on Integration Service Project & Enter Project Name, setting the project location, and clicking OK.

The Project is created.

3. In this sample project, we will transfer QuickBooks data using the ADO.NET source to the Flat File Destination. Wes, we need to add a Data Flow Task in the Control Flow to the perform tab. You can add it by double-clicking on the Data Flow Task.

4. We need to add an ADO.NET Source in the Data Flow tab. You can add it by double-clicking on ADO.NET Source.

5. Now, we need to configure the ADO.NET source. By right-clicking on ADO.NET Source & click on Edit.

Add a new ADO.NET connection by clicking on New.

Add a new Data connection by clicking on New.

Select Provider to .Net Providers\Odbc Data Provider, select DSN to QuickBooks Data QRemote, and click on Test Connection.

Test Connection Succeeded.

You can select Data Access Mode as Table or view the whole table data. You can also select Data Access Mode as an SQL command for accessing table data with a condition & accessing report data using sp_report. In this example, I have selected Table or view as Data Access Mode & selected the Customer table. Click on OK & you will notice the connection has been added.

You can preview output data by clicking the Preview button.

Close the Preview by clicking the close button & click on OK to save configurations.

6. We need to add a Flat File Destination in the Data Flow tab. You can add it by double-clicking on Flat File Destination.

7. Now, we need to link the ADO.NET Source with the Flat File Destination by dragging the link from the ADO.NET Source to the Flat File Destination.

8. Now, we need to configure the Flat File Destination. By right-clicking on Flat File Destination & click on Edit.

Add a new Flat File connection by clicking on New.

Select Flat File Format & click OK.

Select the Destination file you want to store output using the Browse button.

Enable Unicode & Column names in the first data row option, & Click on OK to save configurations.

You will notice the OK button is disabled. To enable it, you need to click on Mapping, then click OK to complete the configuration.

9. Run the SSIS package to perform the transfer operation by clicking the play icon.

SSIS Package execution completed & 163 rows are transferred from ADO.NET Source to Flat File Destination.

Here is a Flat text file that contains the ADO.NET source result.

Please click here to download the Sample SSIS Package.

Problem Description:

I am evaluating your driver and have had success running SELECT queries against QuickBooks in SSMS, where I could use the QRemote DSN. When setting up the ODBC connection in SSIS, I get an error when enumerating the columns.

Unknown Data type found in column

Solution:

To resolve this error, you need to select “ADO.NET Source” instead of ODBC Source in the SSIS package.

Problem Description:

I was able to use QODBC Online. Suddenly, I got the following error when I tried to connect to QuickBooks Online using QODBC Online. It was working properly—no known changes to Windows or QODBC. Begin Session Failed. S0000 00000 [QODBC] QuickBooks Begin Session Failed. Error - Unauthorized-401 - - Fault Exception of type: AUTHENTICATION has been generated.

Solution:

The authorized access token for QuickBooks Online will remain active for 180 days. A privileged access token expires after 180 days. When this occurs, responses to calls to QuickBooks Data Services and the QuickBooks Online API indicate that the access token is invalid.

So, you need to reauthorize/reconnect QODBC Online at QuickBooks Online to resolve the issue.

Please refer to How to Reconnect QODBC Online with QuickBooks Online Edition.

Please follow the steps below.

1) "Disconnect from QuickBooks" 32-Bit.

Start>>All Programs>> QODBC Driver for QuickBooks Online>> Configure 32-bit QODBC Online Data Source>> Go To "System DSN" Tab>> Select "QuickBooks Online Data" of type 32-bit >> Click "configure" >> Switch to "General" tab >>
Click the "Disconnect from QuickBooks" button.

2) "Disconnect from QuickBooks" 64-Bit.
Start>>All Programs>> QODBC Driver for QuickBooks Online>> Configure 64-bit QODBC Online Data Source>> Go To "System DSN" Tab>> Select "QuickBooks Online Data" of type 64-bit >> Click "configure" >> Switch to "General" tab >>
Click the "Disconnect from QuickBooks" button.

3) Close all the applications.

4) Connect to QuickBooks:

Start>>All Programs>> QODBC Driver for QuickBooks Online>> Configure 32-bit QODBC Online Data Source>> Go To "System DSN" Tab>> Select "QuickBooks Online Data" of type 32-bit >> Click "configure" >> Switch to "General" tab >>
Click "Connect to QuickBooks"

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

5) Use the QODBC Online 32-Bit Test Tool to test the connectivity.


6) Export the connection key from "QuickBooks Online Data" DSN of type 32-bit 

Please use the DSN "QuickBooks Online Data" of type 32-bit to export the connection key:
Start>>All Programs>> QODBC Driver for QuickBooks Online>> Configure 32-bit QODBC Online Data Source>> Go To "System DSN" Tab>> Select "QuickBooks Online Data" of type 32-bit >> Click "configure">> Switch to "General" tab >> Click on "Export Connection key" button to the Export key.

7) Import the connection key from the above step to the 64-bit DSN.

Please use the DSN "QuickBooks Online Data" of type 64-bit using 64-Bit ODBC Data Source.
You can import the connection key:
Start>>All Programs>> QODBC Driver for QuickBooks Online>> Configure 64-bit QODBC Online Data Source>> Go To "System DSN" Tab>> "QuickBooks Online Data" of type 64-bit >> Click "configure">> Switch to General tab, click on "Import Connection key" button.

Refer to the knowledgebase article at https://qodbc.com/links/2658 Section "Import / Export connection key:"

8) Use the QODBC Online 64-Bit Test Tool to test the connectivity.

Tags: QuickBooks Online, QBO, Authorization, Authentication, 401, Begin Session Failed

#include <iostream>
#include <windows.h>
#include <sql.h>
#include <sqlext.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <conio.h>

using namespace std;

void ConvertTimeStampStructToString(TIMESTAMP_STRUCT tTimeStamp, CHAR *strTimeStamp, LONG lSizeTimeStamp)
{
strcpy(strTimeStamp, "");
sprintf(sr timestamp, "%d-%d-%d %d:%d:%d," tTimeStamp.year, tTimeStamp.month, tTimeStamp.day, tTimeStamp.hour, tTimeStamp.minute, tTimeStamp.second);
}

int main()
{
SQLHENV henv = SQL_NULL_HENV; // Environment
SQLHDBC hdbc = SQL_NULL_HDBC; // Connection handle
SQLHSTMT hstmt = SQL_NULL_HSTMT; // Statement handle

SQLCHAR sListId[256] = "";
SQLCHAR sEditSequence[256] = "";
SQLCHAR sName[256] = "";
BOOL bIsActive = 0;
TIMESTAMP_STRUCT tTimeModified = {0};
TIMESTAMP_STRUCT tTimeCreated = {0};
SQLINTEGER cbData;

SQLRETURN retcode;
int iKey;

CHAR *sTimeStamp = new CHAR[32]();

SQLCHAR statement[]="SELECT * FROM ShipMethod";

retcode = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
if(retcode != SQL_SUCCESS){
cout << "SQLAllocHandle failed. exit program" << endl;
return 0;
}
cout << "SQLAllocHandle: Environment handle initialized." << endl;

retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION,(SQLCHAR *)(void*)SQL_OV_ODBC2, -1);
if(retcode != SQL_SUCCESS){
cout << "SQLSetEnvAttr failed. exit program" << endl;
return 0;
}
cout << "SQLSetEnvAttr : ODBC 2.0 initialized." << endl;

retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc);
if(retcode != SQL_SUCCESS){
cout << "SQLAllocHandle failed. exit program" << endl;
return 0;
}
cout << "SQLSetEnvAttr: Database handle initialized." << endl;

retcode = SQLSetConnectAttr(hdbc, SQL_LOGIN_TIMEOUT, (SQLPOINTER)10, 0);
if(retcode != SQL_SUCCESS){
cout << "SQLSetConnectAttr failed. exit program" << endl;
return 0;
}
cout << "SQLSetConnectAttr : Set Login Timeout." << endl;

retcode = SQLConnect(hdbc, (SQLCHAR*) "QuickBooks Data" , SQL_NTS, (SQLCHAR*) NULL, 0, NULL, 0);
if(retcode != SQL_SUCCESS){
cout << "SQLConnect failed. exit program" << endl;
return 0;
}
cout << "SQLConnect : Database connection successfully." << endl;

retcode = SQLAllocHandle( SQL_HANDLE_STMT, hdbc, &hstmt);
if(retcode != SQL_SUCCESS){
cout << "SQLAllocHandle failed. exit program" << endl;
return 0;
}
cout << "SQLAllocHandle : Handle initialized." << endl;

retcode = SQLExecDirect(hstmt, statement, SQL_NTS);
if(retcode != SQL_SUCCESS){
cout << "SQLExecDirect failed. exit program" << endl;
return 0;
}
cout << "SQLExecDirect : Query executed successfully." << endl;

cout << endl << endl << endl;
cout << "Query: SELECT * FROM ShipMethod " << endl;
cout << endl << endl << endl;
cout << "ListId" << ", " << "TimeModified" << ", " << "TimeCreated" << ", " << "EditSequence" << ", " << "Name" << ", " << "IsActive" << endl << endl;
cout << endl << endl;
while(SQLFetch(hstmt) == SQL_SUCCESS){

retcode = SQLGetData(hstmt, 1, SQL_C_CHAR, (SQLPOINTER)sListId, sizeof(sListId), &cbData);

retcode = SQLGetData(hstmt, 2, SQL_C_TIMESTAMP, (SQLPOINTER)&tTimeModified, sizeof(tTimeModified), &cbData);

retcode = SQLGetData(hstmt, 3, SQL_C_TIMESTAMP, (SQLPOINTER)&tTimeCreated, sizeof(tTimeCreated), &cbData);

retcode = SQLGetData(hstmt, 4, SQL_C_CHAR, (SQLPOINTER)sEditSequence, sizeof(sEditSequence), &cbData);

retcode = SQLGetData(hstmt, 5, SQL_C_CHAR, (SQLPOINTER)sName, sizeof(sName), &cbData);

retcode = SQLGetData(hstmt, 6, SQL_C_BIT, (SQLPOINTER)bIsActive, sizeof(bIsActive), &cbData);

cout << sListId << ", ";
ConvertTimeStampStructToString(tTimeModified, sTimeStamp, sizeof(sTimeStamp));
cout << sTimeStamp << ", ";
ConvertTimeStampStructToString(tTimeCreated, sTimeStamp, sizeof(sTimeStamp));
cout << sTimeStamp << ", ";
cout << sEditSequence << ", ";
cout << sName << ", ";
cout << bIsActive << endl;
}
delete [] sTimeStamp;
cout << endl << endl;

retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmt);
if(retcode != SQL_SUCCESS){
cout << "SQLFreeHandle failed. exit program" << endl;
return 0;
}
cout << "SQLFreeHandle : Handle freed." << endl;

retcode = SQLDisconnect (hdbc);
if(retcode != SQL_SUCCESS){
cout << "SQLDisconnect failed. exit program" << endl;
return 0;
}
cout << "SQLDisconnect : Close database connection." << endl;

retcode = SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
if(retcode != SQL_SUCCESS){
cout << "SQLFreeHandle failed. exit program" << endl;
return 0;
}
cout << "SQLFreeHandle : Database handle freed." << endl;


retcode = SQLFreeHandle(SQL_HANDLE_ENV, henv);
if(retcode != SQL_SUCCESS){
cout << "SQLFreeHandle failed. exit program" << endl;
return 0;
}
cout << "SQLFreeHandle : Environment handle freed." << endl;

printf("Press Any Key To Exit...");
getch();
return 0;
}

Please click here to download the C++ code.

Problem Description:

I have a pass-through query for access:

Select * from Item

The connection string is as follows:

ODBC;DRIVER={QODBC Driver for QuickBooks};SERVER=QODBC;DFQ=x:\QuickBooks\MyQBcompanyfile.qbw;OpenMode=F;OLE DB Services=-2;OptimizerOn=No;

This works on pc #1 if the QuickBooks file is open OR closed (desired behavior).

This ONLY works on pc #2 if the QuickBooks File is closed.

Why is it operating differently?? I am using the same access file on both pc.

I need this to be running on some computers in the office. Some computers are allowed to use QuickBooks, and some are not, so I need a flexible DSN connection string that will work for both circumstances.  

Solution:

Please verify the company file path from the non-working machine. The other computer might be accessing the company file mapped via network name, i.e., \\servername\folder\ (e.g., \\QuickBooksfileserver\QuickBooks\MyQuickBookscompanyfile.qbw ) when the connection string is using a mapped drive, i.e., x:\

Please start QuickBooks from the non-working machine, log in to the company file, press F2, verify if the file path is the same in the connection string & test again.

Problem Description:

I am using MS Access. I have the integrated application certificate set up correctly (see screenshot). The username for this certificate is "odbc."



QuickBooks is closed.

Ms Access file connects to QuickBooks via the connection string:

"ODBC;Driver={QODBC Driver for QuickBooks};DFQ=D:\QuickBooks\MyCompanyFile.qbw;OptimizerOn=No;IAppAutomaticLogin=n;OpenMode=F;OLE DB Services=-2;"

Connection works.

Another user tries to log in as "Admin" into QuickBooks on another computer, but it fails and says already logged in. See screenshot.



Why is QODBC using the "Admin" account?? I was expecting it to use the "odbc" account.

Solution:

You need to remove QODBC integrated application entries in QuickBooks & companyfilename. lgb and delete it to resolve the issue.

Please refer to Connection Lost Between QODBC and QuickBooks. QuickBooks Asking for Password for more details.

Problem Description:

I am trying to connect to QuickBooks using QODBC. At a time of connection, QuickBooks Displays a Revoked Certificate Warning.

Solution:

Please update your QODBC to the latest QODBC version and test again.

Please click here to get the latest QODBC version.

If you are still getting the same error after updating the version, please check the digital signature of the application you are using, like Crystal Reports or Excel.

For Example:

If you are using MS Excel and getting errors, please check the digital signature in MS Excel.

Open the task manager, right-click on EXCEL.EXE, and click on Open File Location.

You will be navigated to the application location. In this example, we will navigate to the Excel exe location.

Once we reach the exe location, we must right-click on the exe and click on Properties. We will right-click on EXCEL>EXE in this example and click on Property.

Navigate to the Digital Signatures tab & click on Details.

Click on View Certificate to see certificate validity details.

You can see the certificate validity details.

If your application's Digital Certificate validity has expired, you need to get in touch with the Application Vendor to resolve the issue.

Windows Enforcement of Authenticode Code Signing and Timestamping

On Windows 7 platforms and above, the following are new guidelines from Microsoft:

• Microsoft will no longer allow new SHA-1 code signing certificates to be used for signing files on Windows 7 and above starting Jan. 1, 2016.
• Files signed previously with an SHA-1 certificate will continue to work on Windows 7 and above for an additional year as long as they were time-stamped before January 1, 2016.
• Windows 7 and Server 2008 R2 will require a hotfix for SHA-256 support.
• Starting on Jan. 1, 2017, all SHA-1 signed files would be blocked on Windows 7 and above, regardless of when they were time-stamped.

On Vista and Server 2008 platforms:

• Microsoft will execute end-of-life support for Windows 2004 in April 2017 and Server 2008 in January 2020.
• SHA-1 certificates will be supported through the end-of-life for these operating systems.
• There will be limited support for SHA-256 on these platforms, requiring a patch and only allowing downloads or installations of SHA-256 signed content.

Microsoft TechNet:
Windows Enforcement of Authenticode Code Signing and Timestamping

On Vista and Server 2008 platforms:
Microsoft Authenticode - Dual Code Signing Instructions with SHA1 & SHA256 hashing Algorithm


For more details, refer:
Microsoft Windows SHA-1 & SHA-2 Code Signing Hash Algorithm Support
SSL News
SHA-1 Hash Algorithm Migration for SSL & Code Signing Certificates
SHA-1 Deprecation, On to SHA-2

Also, refer to the following:

Revoked Certificate Errors With QuickBooks Desktop Apps

Problem Description:

How do I share/invite the FLEXquarters Support team to access my QBO company file? 

Solution:

Please follow the steps below to share/invite the FLEXquarters Support team to the QuickBooks Online company file.

1. You can share your QuickBooks Online company file connection key by exporting the connection key.

Please refer to the Import / Export connection key section for more details

2. Email the connection key to the FLEXquarters Support team.

3. Log in to https://qbo.intuit.com/ using your credentials.

4. Click on Company Name & Manage Users.

5. Go to the Manage Users section & click on New.

6. Choose user type, select Regular or custom user & click Next.

7. Set the user's access rights, select All & click Next.

8. Set the user's administrative rights. Select User management to "No," Company Information to "View Only," Subscription & Billing to "View subscription information," & click Next.

9. Enter the FLEXquarters Support team Email address support@qodbc.com, First Name to "QODBC," the Last Name to "Support," & click Next.

Click Finish & you're done.

10. QODBC Support is listed under the Manage Users list as an Invited status.

11. Once we accept the invitation, the status will change to Active.

12. You can delete an invited user by selecting the user & click on Delete.

13. By clicking Invite Accountant, you can share/invite the FLEXquarters Support team to access the QuickBooks Online company file from the Accounting Firms section.

14. Enter the FLEXquarters Support team Email address support@qodbc.com, First Name to "QODBC," the Last Name to "Support," & click Next.

Click Finish & you're done.

15. QODBC Support is listed under the Accounting Firms list as an Invited status.

16. Once we accept the invitation, the status will change to Active.

17. You can delete an invited user by selecting the user & click on Delete.

Tags: QuickBooks Online, QBO, QODBC Online

For MS Access 64-bit, please refer to: How to Configure QODBC to Work With 64-bit MS Access

Set up QODBC to use with MS Excel 2016

Note: QODBC allows you to quickly merge live QuickBooks data into the cells of your Microsoft Excel worksheets for quick calculations and graphs. The data will retain a live link to QuickBooks, and one click will update the worksheet to the most current data in the linked QuickBooks table.

Before using the MS Excel application, please make sure you have installed the MS Office Component named "Microsoft Query." About MS Query, please refer to Microsoft Office with MS Query and QODBC for more.

Before starting, please make sure you have the 64-bit version of MS Excel:

First, please select the "Data" tab, navigate to  "From Other Sources"->" From Microsoft Query."

Note: In recent versions of Microsoft Excel (including Excel 365), the Microsoft Query (Legacy) feature is hidden by default from the Get Data tab.
Please refer to Troubleshooting - How to enable Microsoft Excel 365 - Legacy Microsoft Query.

And then, in the "Choose Data Source" Window, please select a DSN to continue. (Here, I choose the default data source with a sample company file open. And check to use the Query Wizard to create/edit queries.

'QuickBooks Data 64-bit QRemote' as an example:

NOTE: If you are using QODBC Online, please select "QuickBooks Online Data 64-bit" instead of "QuickBooks Data 64-bit QRemote".

The first time you use MS Excel to access QuickBooks, you will be asked to grant access permission for this application:

Select the "Yes, always" option and click the "Continue" button. In the next window, click the "Done" button to finish authorizing.

Import QuickBooks data into MS Excel via MS Query

After you grant permission for QODBC, you will be guided by the Query Wizard. In the Choose Columns window, select a table and the columns you want to import. Choose the table you wish to import and select the columns from the table to import by pressing the ">" button. (Here, I choose the table Customer as a sample.) You can add or remove columns from the correct list "Columns in your query."

You can set a filter for your query in this window. If you don't want to set any query, please click the "Next" button:

After the setup is finished, MS Excel will ask you to choose an edit method for the records:

Return Data to Microsoft Excel:

This method will directly export the data to Excel, where you can view and edit these records, but the data is static. The modification will not be uploaded to QuickBooks.

You can view the detailed connection properties by clicking the "Queries & Connections" button in the Data menu:

In the Workbook Connection Window, Right-click on the connection name & click the "Properties" button to view detailed information:

Now you can view the connection string and its SQL statement in the definition window:

View Data or Edit Query in MS Query:

This method will lead you to the MS Query window, and you can view or edit data via SQL Statement.

Click the "SQL" button to view the SQL Statement of this query:

The SQL window will show the SQL Statement, and the user can also modify the statement to extract other records:

The desired record set contains only the records with a Name having a value equaling "Abercrombie, Kristy." Select the field header name and click on it, followed by selecting Criteria -> Add Criteria. In the popped-out Add Criteria window, specify the criteria Field as "Name," Operator as "equals," then click the Value button, and from the list of values, select "Abercrombie, Kristy" -> OK -> Add.

The following screen reflects the applied criteria to the query and the resulting QuickBooks recordset:

When you finish the query, choose to save so that next time, you can directly use the same question:

Leaving MS Query, MS Excel will ask you to import the query result into MS Excel:

     Clicking Data -> Refresh Data or clicking the External Data toolbar will update the data in the worksheet from the latest information in the linked QuickBooks tables, as shown above. Changes to the QuickBooks files will not affect this worksheet until you refresh the data with the Refresh option.

Sample Files: 

Excel - Customer & Company Tables - Download

Excel - Majority of the Tables and Reports - Download

Also, Refer:
How to Use QODBC with MS Excel 2007
Using QuickBooks Data with Excel 2013 32-bit

Keywords: create odbc connection, Office 2013, Office 365, Excel 365, Access 365, Office 2016, Access 2016, Excel 2016, Microsoft Excel 2013 blank window

For 32-bit, please refer to how to configure QODBC to Work With 32-bit MS Access.

Creating a Table in Microsoft Access:

Note: Microsoft Access has many uses and will allow you to use your QuickBooks data files similarly to Access databases.

Please make sure QRemote Server is running. You can find the QRemote Server running in the System Tray. 

If it is not running, then please start QRemote Server from the following:

QODBC Desktop - Start>>All Programs>> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

QODBC Online - Start>>All Programs>> QODBC Driver for QuickBooks Online >> QRemote Server for QODBC Online

QODBC POS - Start>>All Programs>> QODBC Driver for use with QuickBooks POS >> QRemote Server for QODBC POS

Open MS Access 2016, and make sure you are using the 64-bit version of MS Access from:

File->Account->About Access

A default database filename, Database1, appears in the box. You can edit this to a more relevant name, such as QuickBooks Link. accdb. Save the file as type "Microsoft Office Access Databases."

Then, click "Create" to create a blank desktop database:

In the newly created database, you will find a default blank table. Please close this default table:

You could directly extract QuickBooks records into this table. But in this article, we will show you how to build a linked table to access QuickBooks.

Build a connection via the ODBC database button in the External Data menu:

OR

Build a connection via External Data -> New Data Source -> From other sources -> ODBC Database :

Under the Get External Data window, you will see two options:

Link to the data source by creating a linked table: this option will create a table just like the first option,n but will keep its link to QuickBooks, which means all your operations to this table will be uploaded to QuickBooks, and the data in the table is also in full sync with QuickBooks.

This article will show you how to build a linked table in MS Access.

Build a Linked Table in MS Access

After you select the access method and click OK, you will get a Select Data Source window:

Select the QuickBooks-related DSN you set up with the QODBC driver. This can be one of our pre-installed DSN names or one that you have created. (Here, I choose the default DSN as an example.)

NOTE: QODBC Online users, please select "QuickBooks Online Data 64-bit" instead of "QuickBooks Data 64-bit QRemote". QODBC POS users, please choose "QuickBooks POS Data 64-bit" instead of "QuickBooks Data 64-bit QRemote".

The first time you use MS Access to access QuickBooks, it will ask you to grant permission for this application:

Select the "Yes, Always" option, and then click "Done" in the next window:

Once the connection is built, Access will return a list of available tables in the Select Tables window. Please select the tables you want to extract. Multiple Selection is available.

After the Linking table is successful, you will see linked tables created in your MS Access file under "Tables":

You can view the properties of these linked tables by right-clicking the linked table-> selecting linked table manager:

If you want to view QuickBooks records in this linked table, double-click the attached table, and you will see the records:

Note: If you see ###### in the linked table result, you need to increase the column header size. So you can see the actual result.

The linked table is always in sync with QuickBooks Data, so you cannot add or delete any columns in this table. But you can directly modify the data in the linked table, and QODBC will automatically update the modification to QuickBooks.

Note: When you run an application that is not entirely ODBC compatible, they often support getting data from Access tables. To make this application work with QuickBooks tables, you can run the Microsoft Access setup, as shown above. Then have this application use the MS Access ODBC driver to talk to the Access database you created, which was linked to QuickBooks tables. This middleware approach allows us to support nearly any application, even if not fully ODBC compliant.

Please refer to how to use MS Access as Middleware with QODBC for using MS Access as Middleware. 

Suppose you want to import a table into Access. In that case, you have to select Import the source data into a new table in the current database option instead of a link to the data source by creating a linked table & repeat the above steps: this option will directly extract tables into Access Database, you can view and edit these tables, but all modification will not be uploaded unless you build another query to do so.

Also, Refer:
How to Use QODBC with Microsoft Access 2007
Using QuickBooks Data with Access 2013 (Import Tables) 32-bit
Using QuickBooks Data with Access 2013 (Linked Tables) 32-bit
How to Configure QODBC to Work With 64-bit MS Access
Microsoft Access 2003 and QODBC

Keywords: create odbc connection, Office 2013, Office 365, Excel 365, Access 365, Office 2016, Access 2016, Excel 2016

Problem Description:

I am trying to connect to QuickBooks/QuickBooks POS using QRemote Server, but QRemoteServer is Having on Connection.

Solution:

Please check if QuickBooks or QuickBooks POS has a Certificate Popup.

In the QuickBooks POS certificate, pop-up windows go in the background, so you need to check the pop-up window in the background & accept the certificate.

OR

Try Restarting QRemoteServer.
Close/Exit QRemoteServer. You can find the QRemote Server running in the System Tray.

Go to File Menu -> Exit -> :

Do you want to close the QRemote Server? You will get a pop-up window with the message. Please click "OK" to close QRemoteServer.

Please rerun QRemoteServer & test. You can QRemoteServer from:
Start>> All Programs >> QODBC Driver for use with QuickBooks POS >> QRemote Server for QODBC POS

Start>> All Programs >> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

OR

Remove QODBC POS/QODBC-related certificates from QuickBooks POS/QuickBooks.

Please refer to How to remove QODBC Related Certificates from Integrated Application Under QuickBooks POS for more details.

For more details, please refer to How to remove QODBC Related Certificates from Integrated Application Under QuickBooks.

Restart QRemoteServer using the above steps, connect again,n and accept the certificate.

Problem Description 1:

I recently installed QODBC to get data out of a QuickBooks company file, but I get this error: "Index was outside the bounds of the array."

Problem Description 2:

We are attempting to import tables into SQL Server, which we use as a staging environment. We are not doing any transformations, simply trying to copy the data from QuickBooks into SQL Server using the Import Wizard. Below is the screenshot of the error we receive when attempting to do so. Details of the configuration are provided below.

Source data (QuickBooks): Microsoft .NET provider for ODBC - QODBC 32-bit configured DSN with default settings. Destination Data ( SQL Server): Microsoft OLEDB provider for SQL Server

We are attempting to import four tables for now.

- Account, Class, Entity, Transactions

The reported error below occurs for each table.

Error: Can not load the column attributes from the schema for the current provider descriptor.
- COLUMN_NAME
- TYPE_NAME
- COLUMN_SIZE
- DECIMAL_DIGITS
- COLUMN_SIZE

Solution:

Please follow the steps below to resolve this error:

1. Go to Import Export Wizard by right-clicking on your SQL Server database, clicking on Task, & Click on Import Data.

2. Choose ODBC Data Source & Enter DSN & Connection String, and click "Next."

3. Choose Destination and click on "Next."

4. Choose the second option (Write a query to specify the data to transfer) and click "Next."

5. Write the query and click on "Next." You can change the table name & question as per your requirement.
For Example:
Select * from the Account

6. Change the destination table name to your requirement and click "Edit Mapping."

7. You must verify the date type of all columns from the "Type" column.

You need to make sure that you are not getting 23 in Type. You will get 23 date-type columns.

You need to replace 23 with the current date for all columns whose Type is 23 and click on "OK."

8. Click on "next" until the finish.

Save and Run Package.

Complete the Wizard.

9. You can see the table data imported to SQL Server's local database table.

Keywords: How to use DTS to import QuickBooks Data into MS SQL Server

Please follow the steps to remove QODBC-related certificates from the Integrated Application Under QuickBooks POS:

Try removing all the integrated application entries in QuickBooks POS again via File Menu -> Preferences -> Company -> Integrated Applications Tab.

Switch to Integrated Applications

To know which application uses "QODBC POS" to communicate with QuickBooks POS.

You can check it from the Application ID & File Name.

To Remove, Select "QODBCPOS-APPLICATION," For Example, "QODBCPOS-MSACCESS.EXE," Click Remove and Save.

( If there are Multiple "QODBCPOS-APPLICATION" Listed, you may remove a single Integration at a time.)

Exit QuickBooks POS.

Please start QuickBooks POS and log in again to your Company file.

Problem Description:

I have a custom program written in Access 2003 communicating with QuickBooks 2013 using QODBC 13, which works fine. Will upgrading to the latest QuickBooks and QODBC require any code changes to the Access 2003 program?

Problem Description:

We are upgrading from QuickBooks Pro 2011 to QuickBooks Enterprise (the latest) and need a developer/consultant to assist in checking/upgrading queries and code to work with the new versions of QODBC/QuickBooks. Our company uses the QODBC Driver for QuickBooks to synchronize data between our Microsoft Access database and QuickBooks. We push customers, jobs, cheques, and items from Access to QuickBooks and pull data from QuickBooks to Access for reports.  

Solution:

It is unlikely that you will have a problem as QODBC is upward compatible with QuickBooks, so the same queries you have running now should continue to work.

Suggest you purchase the latest version of QODBC, which supports the newest version of QuickBooks, then run some tests. If you have any trouble with connections, please refer to the following:

Connecting QODBC Driver to QuickBooks for the First Time (Video)
How to Use QODBC with Microsoft Access 2010 to Build Linked Table(32-Bit)
How to Configure QODBC to Work With 64-bit MS Access

Or Raise a Support Ticket

There shall be no code change required in your MS-Access Application/Queries, and it should be able to work with the latest QuickBooks & QODBC.

Additional Information:
With every release of QuickBooks/QODBC, new fields or features might be added. If you want to leverage the new areas, you will have to re-link the tables in Access. Refer: How to Re-Link QuickBooks Data in MS Access using QODBC.

Please refer to the link below for details about the updated QODBC table & report schema and the relation between tables. You will also get information on each report column parameter that is supported. You can also view all table/column details.

Please refer to QODBC Data Layout for more details.

Note: QODBC allows you to quickly merge live QuickBooks data into the cells of your Microsoft Excel worksheets for quick calculations and graphs. The data will retain a live link to QuickBooks, and one click will update the worksheet to the most current data in the linked QuickBooks table.

Open the QODBC setup screen and change the QODBC Compatibility mode from "Default" to "3.8."

To change, please follow the steps below:

Start >> All Programs >> QODBC Driver for QuickBooks >> Configure QODBC Data Source >>Go To "System DSN" Tab>> click the DSN "QuickBooks Data" >> click "Configure”>> Switch to "Advanced" tab>> Navigate to "QODBC Compatibility">> change to "3.8"

Note: This should fix the "Driver does not support this parameter" error message.

Similarly, change the DSN configuration for QRemote 32-Bit and QRemote 64-Bit.

QRemote 32-Bit
Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >>Go to "System DSN" Tab>> select "QuickBooks Data
QRemote" DSN > click "Configure">> Switch to the Advanced tab and change 'ODBC Compatibility' to '3.8' and click the Apply/OK button.

QRemote 64-Bit
Start >> All Programs >> QODBC Driver for use with QuickBooks (64-Bit)>> Configure QODBC Data Source >>Go to "System DSN" Tab>> select "QuickBooks Data 64-bit QRemote" DSN >> click "Configure">> Switch to Advanced tab and change 'ODBC Compatibility' to '3.8' and click the Apply/OK button.

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

Before using the MS Excel Power Query application, please make sure you have installed the MS Excel Add-in named "Power Query."

Please select Power Query Window.

Please select the data input method via From Other Sources & click on From ODBC.

Note: In recent versions of Microsoft Excel (including Excel 365), the Microsoft Query (Legacy) feature is hidden by default from the Get Data tab.
Please refer to Troubleshooting - How to enable Microsoft Excel 365 - Legacy Microsoft Query.

In the connection string box, write "DSN = QuickBooks Data" & in the SQL Statement box, write your SQL statement & click on the "OK" button. If you have 64-bit MS Excel, then you need to write DSN = QuickBooks Data 64-bit QRemote in the connection string box.

Now select the "Windows" & "Use my current credentials" option and click on the "OK" button.:

Now you will get data in Power Query, apply the filter & other settings as per your requirement & click on the "Close & Load" button.

If you are facing the error "ODBC: ERROR [HYC00] [Microsoft][ODBC Driver Manager] Driver does not support this parameter", please switch QODBC, QRemote 32-Bit DSN, and QRemote 64-Bit DSN to ODBC Compatibility 3.8

You can also use "From Microsoft Query" for fetching data from QuickBooks to Excel.

For Excel 64-Bit:

http://qodbc.com/links/2771

For Access 64-Bit:
http://qodbc.com/links/2772

Excel 32-Bit:
http://qodbc.com/links/2466

Access 32-Bit:
http://qodbc.com/links/2470

Video tutorial:
http://qodbc.com/links/2509

Also, Refer:
How to Use QODBC with Microsoft Access 2007
Using QuickBooks Data with Access 2010 (Import Tables) 32-bit
Using QuickBooks Data with Access 2010(Linked Tables) 32-bit
How to Configure QODBC to Work With 64-bit MS Access
Microsoft Access 2003 and QODBC

Tags: The driver does not support this parameter.

Note: QODBC does not support direct import, but you can write VBA code that reads a CSV / Excel file & generates insert statements.

There are two ways to import data to QuickBooks through CSV using QODBC.

1) Using Wizard

Create a new MS Access Database file & link the Customer table.

Please refer to Using QuickBooks Data with Access 2016 / 365 / 2013 32-bit for linking the Customer table.

Go to the "External Data" tab on Microsoft Access, as shown in the screenshot below, and click on the "Text File."

The "Get External Data" screenshot will be shown below. Select the CSV file by clicking the "Browse" button. (*Note: the file name must be less than 64 characters. Otherwise, Microsoft Access will not be able to import it. Choose the second option. Append the copy of the records to the table.

Next, select the option "Delimited - Characters such as comma or tab separate each field," as shown in the screenshot below, and click "Next."

Next, make sure "Comma" is selected in the "Choose the delimiter that separates your fields" and the double quotes symbol "s selected in the "Text Qualifier" as shown in the screenshot below, and click "Next" to continue.

Now, click on the Advanced button to configure import fields.

Now write the field name you want to insert from the CSV file & click OK.

Click Finish to complete the import process.

Import Done. Customer data from CSV is inserted into the QuickBooks customer table.

Or

2) Using VBA Code

Please refer to Using QuickBooks Data with VBA

In this tutorial, we are showing a sample VBA script inserting Customer & Invoice.

Importing Customer to QuickBooks through CSV file using QODBC & Microsoft Access VBA

We have a Customer CSV file with Customer Name, Company Name, Phone & Email fields.

We will import these fields to QuickBooks using VBA. You can see the records below from the Customer CSV file.

Please refer to the sample VBA code for Importing Customers to QuickBooks through a CSV file using QODBC.

By clicking on the "Add Customer" button, the Customer list in a CSV file will be imported into QuickBooks using QODBC.

Please Note: You need to change the CSV file location & VBA script according to your CSV file location & file data.

Please refer to the code below code which is used in this example:

Import Customer:

Option Compare Database

Public Sub exampleCsvImportCustomer()

Dim oConnection As New ADODB.Connection
Dim sConnectString
Dim MyArray As Variant
Dim fso As Variant
Dim objStream As Variant
Dim objFile As Variant
Dim sSQL As String
Dim sMsg
Dim rs
Dim I As Integer
i = 0
sConnectString = "DSN=Quickbooks Data;OLE DB Services=-2;"

'' For 64-bit use this one-->sConnectString = "DSN=QuickBooks Data 64-bit QRemote;"

sSQL = "SELECT * FROM customer"

Set rs = New ADODB.Recordset
oConnection.Open (sConnectString)
rs. Open sSQL, Connection, adopt dynamic, adLockOptimistic

Set fso = CreateObject("Scripting.FileSystemObject")

If fso.FileExists("C:\Input\Customer.csv") Then
Set objStream = fso.OpenTextFile("C:\Input\Customer.csv", 1, False, 0)
End If

Do While Not objStream.AtEndOfStream
strLine = objStream.ReadLine
ReDim MyArray(0)
MyArray = Split(strLine, ",")
rs.AddNew
rs("Name") = MyArray(0)
rs("CompanyName") = MyArray(1)
rs("Phone") = MyArray(2)
rs("Email") = MyArray(3)
rs.Update
i = i + 1

Loop

sMsg = sMsg & "Customer Added!!!"
MsgBox sMsg

End Sub

Please Note: If you have a 64-bit application, then you need to use QRemote 64-bit DSN "QuickBooks Data 64-bit QRemote" (i.e., sConnectString = "DSN=QuickBooks Data 64-bit QRemote; OLE DB Services=-2;")

Importing Invoice to QuickBooks through CSV file using QODBC & Microsoft Access VBA

We have an Invoice CSV file with CustomerRefListID, RefNumber, InvoiceLineItemRefListID, InvoiceLineDesc, InvoiceLineRate, InvoiceLineQuantity, InvoiceLineSalesTaxCodeRefListID & FQSaveToCache fields.

In this example, we are creating two Invoices, each having 3 invoice lines. We will import these fields into QuickBooks using VBA. You can see the records below from the Invoice CSV file.

Please refer to the sample VBA code for Importing Invoices to QuickBooks through a CSV file using QODBC.

By clicking the "Add Invoice" button, the Invoice list in a CSV file will be imported into QuickBooks using QODBC.

Please Note: You need to change the CSV file location & VBA script according to your CSV file location & file data.

Please refer to the code below code which is used in this example:

Import Invoice:

Option Compare Database

Public Sub exampleCsvImportInvoice()
Dim oConnection As New ADODB.Connection
Dim sConnectString
Dim MyArray As Variant
Dim fso As Variant
Dim objStream As Variant
Dim objFile As Variant
Dim sSQL As String
Dim rs
Dim sMsg
Dim I As Integer
i = 0

sConnectString = "DSN=Quickbooks Data;OLE DB Services=-2;"

'' For 64-bit use this one-->sConnectString = "DSN=QuickBooks Data 64-bit QRemote;"

sSQL = "SELECT * FROM InvoiceLine"

Set rs = New ADODB.Recordset
oConnection.Open (sConnectString)
rs.Open sSQL, oConnection, adOpenDynamic, adLockOptimistic

Set fso = CreateObject("Scripting.FileSystemObject")

If fso.FileExists("C:\Input\Invoice.csv") Then
Set objStream = fso.OpenTextFile("C:\Input\Invoice.csv", 1, False, 0)
End If

Do While Not objStream.AtEndOfStream
strLine = objStream.ReadLine
ReDim MyArray(0)
MyArray = Split(strLine, ",")
rs.AddNew
rs("CustomerRefListID") = MyArray(0)
rs("RefNumber") = MyArray(1)
rs("InvoiceLineItemRefListID") = MyArray(2)
rs("InvoiceLineDesc") = MyArray(3)
rs("InvoiceLineRate") = MyArray(4)
rs("InvoiceLineQuantity") = MyArray(5)
rs("InvoiceLineSalesTaxCodeRefListID") = MyArray(6)
rs("FQSaveToCache") = MyArray(7)
rs.Update
i = i + 1

Loop

sMsg = sMsg & "Invoice Added!!!"
MsgBox sMsg

End Sub

Please Note: If you have a 64-bit application, then you need to use QRemote 64-bit DSN "QuickBooks Data 64-bit QRemote" (i.e., sConnectString = "DSN=QuickBooks Data 64-bit QRemote; OLE DB Services=-2;")

Download Sample

Also, Refer:

QODBC Reports Architecture Mismatch Problem When connecting

Problem Description:

I have one QuickBooks Online login, which provides access to multiple QuickBooks Online companies.

When I initially configured the connection, I selected one of the clients to which I have access (Company A). The connection worked great, and I got the data I needed. Now I want to export data for another client of mine (Company B), but I'm unsure how to reconfigure it to pull from their database, not Company A's. 

Solution:

You can create a new DSN company-wise & authorize your company file, and use it in your configuration.

For Example, create a new DSN for Company A & use Company A's DSN for accessing Company A's data.

In the same way, you can create a DSN for Company B & use Company B's DSN to access Company B's data.

You can repeat this for multiple company files.

Please refer to the example below, which shows creating a QODBC Online DSN company-wise.

Launch QODBC Online Data Source Configuration

      Locate the QODBC Driver for the QuickBooks Online program group on your desktop. Click on the Configure QODBC Online Data Source icon to create or configure a QODBC Online Data Source Name (DSN).

Create a New DSN

      Click on the System DSN tab to create a DSN that both Windows applications and services can call. Click on the Add button to create a new DSN.

       Select the QODBC Driver for QuickBooks Online option and click on the Finish button.

Configure the Created DSN

      Enter the Data Source Name as CompanyA and click Apply.

Click Connect To QuickBooks

You need to authorize your company file to work with QODBC Online.

During the authorization, select your Company file. 

For more details, please refer to How to Connect QODBC Online with QuickBooks Online Edition.

Once connected, you can use Excel, Access, or QODBC Online Test Tool or any other application, and use "CompanyA" instead of "QuickBooks Online Data." You should be able to connect and fetch data from QuickBooks Online.

You can repeat the above steps for another company file (i.e., CompanyB, CompanyC, et.).

Tags: QuickBooks Online, QBO, Configure online DSN, QODBC Online, connect company files, multiple

Download Sample

Sample Code for using QODBC DSN:

Sample 1

import pyodbc

# Replace with your actual DSN name
dsn_name = 'QuickBooks Data'
print("connecting to the DSN" , dsn_name);
# Connect using the DSN
conn_str = f'DSN={dsn_name};'
conn = pyodbc.connect(conn_str)
print("Connected to the DSN" , dsn_name);
# Create a cursor from the connection
cursor = conn.cursor()
print("Cursor Created");
print("Executing select * from customer");
# Execute the query
cursor.execute("SELECT * FROM Customer")

print("Fetching all");
# Fetch all rows
rows = cursor.fetchall()

print("Getting column");
# Get column names
columns = [column[0] for column in cursor.description]

# Display header (first 5 column names)
print(" | ".join(columns[:5]))

print("Printing column");
# Display each row (first 5 columns)
for row in rows:
print(" | ".join(str(row[i]) for i in range(min(5, len(row)))))

# Clean up
cursor. Close()
conn.close()

Sample 2

import pyodbc 

cn = pyodbc.connect('DSN=QuickBooks Data;')

cursor = cn.cursor()

cursor.execute("SELECT Top 10 Name FROM Customer")

for row in cursor.fetchall():

print (row)

cursor.close()

cn.close() 

QODBC Configuration:

Turn on the "SQL Server Support" and set ODBC Compatibility to "Default". 

OR

Turn on the "Simulate Transaction support for SQL Server" option 

OR

Turn on the "SQL Server Support" option 

Script execution & Result in Command Prompt:

Navigate to your Python script folder:

Run your Python script:

Result:

Troubleshooting:

If you receive an error  [QODBC] Driver Not Capable when using "QuickBooks Data" DSN

To resolve this error, you need to enable the "Simulate Transaction support for SQL Server" or "SQL Server Support"  option from:

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source>>Go To "System DSN" Tab>> select QuickBooks Data>> click "configure">> switch to Advanced tab>> enable "Simulate Transaction support for SQL Server" option.

After enabling the above option, you can use "QuickBooks Data" DSN in the Python script.

Sample Code for using QRemote DSN:

import pyodbc 

cn = pyodbc.connect('DSN=QuickBooks Data QRemote;')

cursor = cn.cursor()

cursor.execute("SELECT Top 10 Name FROM Customer")

for row in cursor.fetchall():

print (row)

cursor.close()

cn.close() 

Please refer to how to configure QRemote.

Please Note: If you have a 64-bit application, you must use QRemote 64-bit DSN "QuickBooks Data 64-bit QRemote."

Script execution & Result in Command Prompt:

Navigate to your Python script folder:

Run your Python script:

Result:

Sample Code for parameterized insert statement using QRemote DSN:

Download Sample

import pyodbc
from decimal import *

stmt = pyodbc.connect("DSN=QuickBooks Data QRemote", autocommit=True)

CustomerRefListID = input("CustomerRefListID: ")
ClassRefFullName = input("ClassRefFullName: ")
TemplateRefListID = input("TemplateRefListID: ")
RefNumber = input("RefNumber: ")
CreditMemoLineItemRefListID = input("CreditMemoLineItemRefListID: ")
CreditMemoLineDesc = input("CreditMemoLineDesc: ")
Rate = input("CreditMemoLineRate: ")
Quantity = input("CreditMemoLineQuantity: ")
Amount = input("CreditMemoLineAmount: ")

encoding = 'utf-8'
P1 = CustomerRefListID.encode(encoding)
P2 = ClassRefFullName.encode(encoding)
P3 = TemplateRefListID.encode(encoding)
P4 = RefNumber.encode(encoding)
P5 = CreditMemoLineItemRefListID.encode(encoding)
P6 = CreditMemoLineDesc.encode(encoding)
P7= Decimal(Rate)
P8= Decimal(Quantity)
P9= Decimal(Amount)

cursor = stmt.cursor()

sql = "INSERT INTO CreditMemoLine (CustomerRefListID,ClassRefFullName, TemplateRefListID, RefNumber,  CreditMemoLineItemRefListID, CreditMemoLineDesc, CreditMemoLineRate,CreditMemoLineQuantity, CreditMemoLineAmount) values (?,?,?,?,?,?,?,?,?)"

cursor.execute(sql,(P1),(P2),(P3),(P4),(P5),(P6),(P7),(P8),(P9))

cursor.close()
stmt.close()

Navigate to your Python script folder:

Run your Python script:

CCredit memowas created in QuickBooks.

Problem Description:

I am trying to do some testing and now have access to a QuickBooks Online Sandbox company. I have tried to connect to it in two different ways.

1. If I "Connect to QuickBooks" on the QODBC Driver for QuickBooks Online Setup Screen without checking the "Sandbox Company" checkbox, I can connect to QuickBooks Online, but cannot see any data from my QuickBooks Online Sandbox company.

2. If I "Connect to QuickBooks" on the QODBC Driver for QuickBooks Online Setup Screen with the "Sandbox Company" checkbox checked, it goes through the QuickBooks Online login screen and presents the Authorize button on the next screen. When I click on Authorize, it closes that screen and opens a new one, which also requests Authorize. When I click Authorize on that screen, too, it then reports "Connection Complete," but it never loads the Access Token, and the "Connect to QuickBooks" button does not toggle to "Disconnect from QuickBooks." When I try to access my Sandbox Company tables using VBDemo, I get the error message shown in the attached file named "Error Message."

I am getting the following error:





Also, I have noticed the following entries in the QODBCOL.log files:

Begin Session Failed. S0000 00000 [QODBC] QuickBooks Begin Session Failed. 658 - Access Token Not Found. Go to [QODBC Online Setup Screen] and click [Test Connection to QuickBooks Online]. Please authorize QODBC Online to connect to your QuickBooks Online Company.

Please advise on the correct process to connect to the Sandbox Company from QODBC.

Solution:

There might be some issues with Intuit's authorization service. Please wait for 30 minutes and try again. You should be able to connect to the Sandbox company file.

Tags: QuickBooks Online, QBO, Sandbox, QODBC Online

For installation & configuring QODBC Online to work with the QuickBooks Online live company file. Please refer:

How to use QODBC Online with QuickBooks Online Edition (Apps.com)

Configure QODBC Online to work with the Sandbox company file:

You need to authorize & configure QODBC Online to work with the QuickBooks Online Sandbox company.

Please follow the steps below to configure QODBC Online:

1) Open QODBC Online Setup Screen & click on "Connect To QuickBooks," & refer to the below step-by-step guide:

Start>>All Programs>> QODBC Driver for use with QuickBooks Online>> Configure QODBC Data Source>> Go To "System DSN" Tab>> select QuickBooks Online Data>> click "configure">> switch to General tab

Enable the Sandbox Company (for testing only) option & click on the "Connect To QuickBooks" button.

2) By clicking "Connect To QuickBooks," open the authorization screen. You need to authorize your company file to work with QODBC Online.

3) You need to enable a pop-up.

4) Enter your QuickBooks User ID & Password, then click "Sign In."

5) Select the sandbox company files you want to use with QODBC Online if you have multiple company files.

6) Click on "Authorize."

7) After successful authorization, it will return to the QODBC Online page with a connected status. You can close this window.

8) QODBC Online is successfully connected to your QuickBooks Online Sandbox company.

9)Now, we will test the connection using the QODBC Online Test Tool. Please open the QODBC Online Test Tool from:
Start>>All Programs>> QODBC Driver for use with QuickBooks Online >>QODBC Online Test Tool

10) Please select the "QuickBooks Online Data" DSN from the dropdown list & click on "Connect."

11) We can connect to DSN from the QODBC Online Test Tool. Please write your SQL statement & click on "Run."

12) We can fetch data from the QODBC Online Test Tool. 

Keywords: sandbox online, QuickBooks Online, QBO, QODBC Online

Problem Description:

We recently upgraded from QODBC 14 to 16.00.00.313. It is functioning normally, except now the QuickBooks window is opening up when it didn't used to. In version 14, it didn't open up QuickBooks while being accessed. Now it does. Is there a way to change this behavior with a setting?

Solution:

Please disable the force start QuickBooks option from the DSN you are using.

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source>>Go To "System DSN" or "User DSN " Tab, whatever you are using > your DSN >> click "configure">> switch to Advanced>> disable Force Start QuickBooks option and try again.

Problem Description:

So the QODBC works excellently running on the machine. We intend to integrate into our website / Intranet to create customers or make changes from the web. I noticed QuickBooks needs to be logged in and open to function. Is there a server version that will not require a user to log in or pass the info along automatically, so the website continues to function correctly?

Is there a way to try the server version by syncing to the SQL server? I need to be able to dump the customer table once daily into SQL. Maybe other tables in the future, like orders or quotes. Does the server version need a remote desktop session open to work? If the server reboots because of an update, I need to log in to make it work again. That doesn’t seem very feasible for us. 

Solution:

QODBC is not a driver you would install on a server; multiple workstations would have access to it. The server version of QODBC is for synchronizing SQL Server with QuickBooks data or for a web or intranet application.

>>Is there a server version that will not need a user logged in or pass the info along automatically, so the website continues to function correctly?
>>Does the server version need to have a remote desktop session open to work?

Please refer to how to Setup QODBC to Access QuickBooks when no one Logged in.

OR

You may configure a session-0 to start and start QuickBooks and QRemoteServer automatically.
When you configure session-0, you are setting up the auto login of a user, and that user will have a desktop session running.

>>Is there a way to try the server version by syncing to the SQL server?

You can use La inked Server on SQL Server and connect to QuickBooks Data using QRemote. When you query the Linked Server/tables, you will always get live QuickBooks Data.

For a dump of all the tables or selected tables from QODBC to Tables in SQL Server Database, you may write a script to create the table(s) in SQL Server and get data from the linked server.

e.g.
SELECT * into LocalSQLTableName FROM OPENQUERY(YourLinkedServerName, 'SELECT * FROM LinkedTableName')

SELECT * into tblVendor FROM OPENQUERY(QRemote, 'SELECT * FROM Vendor')

You can add the script to the agent to run periodically.

Please refer to the below-mentioned article for How to create a Link Server with MS SQL 2005/2008/2012 Using QODBC/QRemote.

For 32-bit SQL Server, refer to:
How to create a Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC/QRemote

For 64-bit SQL Server, refer to:
How to create a Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC/QRemote


Also, Refer:
How to set up QODBC Driver to auto-connect to QuickBooks. (Video)
How to setup QODBC for Auto-login into QuickBooks

Problem Description:

I cannot find or configure the 32-bit ODBC Data Source Manager under a 64-bit System. I will be happy to remotely access you and my server representatives to resolve this.

Solution:

Configure QODBC Data Source is located differently in Operating System wise. Please refer to the steps below according to your Operating System for finding the Configure QODBC Data Source.

Windows 7:

You can locate Configure QODBC Data Source in Windows 7 from:

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source

Go To the "System DSN" Tab

You can locate Configure QODBC Data Source 64-bit in Windows 7 from:

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source 64-bit

Go To the "System DSN" Tab

Windows 8.1 or Windows 2012:

You can locate Configure QODBC Data Source in Windows 8.1 or Windows 2012 by searching "Configure QODBC Data Source":

Click on Configure QODBC Data Source from a search result.

Go To the "System DSN" Tab

You can locate Configure QODBC Data Source 64-bit in Windows 8.1 or Windows 2012 by searching "Configure QODBC Data Source 64-bit:

Click on Configure QODBC Data Source 64-bit from a search result.

Go To the "System DSN" Tab

Windows 10:

You can locate Configure QODBC Data Source in Windows 10 by searching "ODBC Data Sources (32-bit)":

Click on ODBC Data Source 32-bit from a search result.

Go To the "System DSN" Tab

You can locate Configure QODBC Data Source 64-bit in Windows 10 by searching "ODBC Data Sources (64-bit):

Click on ODBC Data Source 64-bit from a search result.

Go To the "System DSN" Tab

Windows Server 2008:

You can locate Configure QODBC Data Source on Windows Server 2008 from:

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source

Go To the "System DSN" Tab

You can locate Configure QODBC Data Source 64-bit in Windows Server 2008 from:

Start>>All Programs>> QODBC Driver for use with QuickBooks>> Configure QODBC Data Source 64-bit

Go To the "System DSN" Tab

Locate QODBC Configure Data Source via Control Panel:

Open Control Panel

Click on Administrative Tools

Click on ODBC Data Sources (32-bit) to open the 32-bit Configure Data Source window.

Go To the "System DSN" Tab

Click on ODBC Data Sources (64-bit) to open the 64-bit Configure Data Source window.

Go To the "System DSN" Tab

Locate QODBC Configure Data Source Directly:

You can run the 32-bit ODBC admin utility to see the data source from:
C:\Windows\SysWOW64\odbcad32.exe

Go To the "System DSN" Tab

You can run the 64-bit ODBC admin utility to see the data source from:
C:\Windows\System32\odbcad32.exe

Go To the "System DSN" Tab

We keep getting the "QuickBooks Begin Session Failed" error when opening a QODBC connection on a web page.
--> It happens when several users are using QuickBooks at the same time.
--> When it happens, we try to use the 'QODBC Test Tool,' and it works fine.
--> When no user or a few users are using QuickBooks, this error is gone.
--> When it happens, we have to reboot the QuickBooks service.

Solution:

Please ensure that your QuickBooks is in running mode and that you are logged in as Admin to the company file.

If QuickBooks is in running mode & you are still facing the issue, please restart your server & try to connect.

Please verify the QRemote connection & try to connect.

You can verify your QRemote DSN configuration:

For 32-bit QRemote DSN:

Start>> All Programs>>QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >>Go To "System DSN" Tab >> select QuickBooks Data QRemote >> click "configure":





Please verify IP & Port from QRemote Client. It should be the same as it is on the QRemote Server.



You can find the QRemote server running in the System Tray.



If it is not running, then please run the following:

Start>>All Programs>> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC



Please verify "Remote DSN" select "QuickBooks Data "DSN from the dropdown>> click "Test Connection" & share the outcome.

For 64-bit QRemote DSN:

Start>> All Programs>> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source 64-bit >>Go To "System DSN" Tab >> select QuickBooks Data 64-bit QRemote>> click "configure":





Please verify IP & Port from QRemote Client. It should be the same as it is on the QRemote Server.



You can find the QRemote server running in the System Tray.



If it is not running, then please run the following:

Start>>All Programs>> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC



Please verify "Remote DSN" select "QuickBooks Data "DSN from the dropdown>> click "Test Connection" & share the outcome.

Problem:

There are multiple company files in QuickBooks. At a time, I can access only one company file. Does QODBC allow me to access multiple company files at the same time?

Solution:

To access data from multiple QuickBooks company files, you must configure a dedicated Data Source Name (DSN) for each individual file. Each DSN should be configured to handle auto-login for its respective company file. For detailed setup steps, please refer to the guide: How to set up QODBC for auto-login into QuickBooks.

To switch between different company files, simply update your application's connection string to point to the specific DSN associated with that company file.

Please refer to How to set up QODBC for auto-login into QuickBooks.

Step 1: Granting QODBC Access Permissions

Before attempting automated data extraction, QODBC must be granted permission by each QuickBooks company file. This configuration is a one-time requirement per company file.

Follow these steps for each file:

1. Open QuickBooks and log into the target company file as a QuickBooks user Admin in Single-User Mode.

2. Connect to the company file using the QODBC Test Tool or your integrated user application.

3. A QuickBooks integrated application certificate prompt will appear.

4. Accept the certificate and grant the necessary permissions to allow QODBC to access the data.

Step 2: Extracting and Consolidating Data

Once all certificates are accepted, you can proceed with data extraction:

1. Use an application such as Microsoft Excel Or Access, or your custom application to connect to each DSN sequentially.

2. Export/dump the required data for the company.

3. Close the connection, and wait for 15 seconds before connecting to the next company file.

Important Technical Limitations

⚠️ QuickBooks SDK Connection Constraint The QuickBooks SDK can only connect to one company file at a time. It does not support concurrent connections to multiple company files.

Because simultaneous access is not supported, your data extraction workflow must strictly follow a sequential connection process. You must completely close the connection to the active company file before opening a connection to the next one.

• Required Delay: To ensure QuickBooks completely releases the previous session, implement a 15 to 30-second delay (gap) between closing Connection A and opening Connection B.

Potential Error Messages

If an application attempts to access multiple company files concurrently, or if a new connection is initiated too quickly without the required delay, the system will return the following error:

If the user tries to access multiple company files at the same time, then you will receive the error:

As a workaround, you can use multiple machines, each with QuickBooks and QODBC installed. Each machine will have a different QuickBooks company file opened in the QuickBooks application. The application machine uses QRemote Client (different DSNs) to connect to those machines and access the QuickBooks company file data simultaneously. 

For Example:
On Application Machine.
QRemote Client DSN A --> Points to the IP Address of Machine A --> Machine A will have QuickBooks company file A opened.

QRemote Client DSN B --> Points to the IP Address of Machine B --> Machine B will have QuickBooks company file B opened.

QRemote Client DSN C --> Points to the IP Address of Machine C --> Machine C will have QuickBooks company file C opened.

Also, Refer to:
How to create or configure a QRemote DSN

 Keywords: QB win log with multiple companies, log in with various companies, multi-instance, Secondary QuickBooks, multiple company files.

Problem Description:

I am getting the following message from Visual Studio 2015 when trying to connect to QRemote using the ODBC data source:

"An error occurred while retrieving the information from the database: Column 'TABLE_CAT' does not belong to table Tables."

We unchecked the box on the server to run 2.1 ODBC compatibility.

The test connection works, and I can access the data using QRemote on my client machine, but I cannot get this database to connect to Visual Studio.

Solutions:

Please query the table directly instead of loading tables.

For Example:

Select * from the customer

Problem Description 1:

My application needs to read data from QuickBooks and update data in the SQL server. Up to this, I can handle everything. But I need a solution for the task scheduler. My need is that my application needs to run every hour through the task scheduler. I'm trying this, but it is giving the error message:

QuickBooks Begin Session Failed. Error = 80040408, Could not start QuickBooks.

Problem Description 2:

I have a batch file that runs a query using the QODBC driver. It ran perfectly when I logged in, but when I ran it as a scheduled task, I got this error:

Unable to connect to QuickBooks Connection String: DSN=BPCQuickBooks _PROD_batch; DFQ=; OpenMode=F; SERVER=QODBC, OLE Automation Error. The source is Microsoft OLE DB Provider for ODBC Drivers." [QODBC] Server Edition of QODBC is required to use the DCOM Servers."

SQLConnect [QODBC] QuickBooks Begin Session Failed. Error = 8004041c, An internal QuickBooks error occurred while accessing the QuickBooks company data file. 

Problem Description 3:

There is a batch script that runs the data extraction, and it works when it is run manually, and we can generate a CSV file. However, when the batch script is scheduled to run using the task scheduler, it gives an error message 8004041d. We have followed all the solutions in the article, and we're still running into the error message when the task runs during the scheduled time in the task scheduler. We can also manually run the task in the task scheduler without an error, so it is only during the scheduled times that it gives an error, Error ID 8004041d

Solution : 

Windows Scheduler has changed from desktop-based to service-based from Vista or Windows 7 onwards, and the new OS has the Scheduler as a service-based. 

QODBC is able to access data from QuickBooks using the QuickBooks SDK, which is an embedded feature of the QuickBooks Desktop Application.

The QuickBooks SDK requires an active desktop session (someone to be logged in) to the machine because QuickBooks is a desktop-based application.

If no one logs on to the server/machine, you will get the error "Could not start QuickBooks."

Even if you have specified the username/password and have a user logged into the machine, you may notice the same error. This is because the task executed from Task Scheduler runs as a different user / new session.

The workaround is to use a Desktop-based Based Scheduler like QScheduler https://qxl1.com/qschedule,  or http://alternativeto.net/software/task-scheduler/?platform=windows. 

How to use QScheduler with QODBC for repetitive or scheduled jobs

You can download QScheduler from the mentioned link:

Download QScheduler

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

After downloading QScheduler, please install it on your machine.

How to use QScheduler - https://qxl1.com/links/3059

Add a new task using the "Add" button.

Enter the task title in the "Task Name", and click the "Browse" icon to select the application.

Input the start date of the task and the frequency.

Select the file that you want to schedule & click "OPEN." In this example, I am selecting the VBS script.

Review the task details and click "Close".

The task will be added to the task list and will be executed.

Windows Task Scheduler (Troubleshooting)

If your company policy requires you to use the default Windows Task Scheduler, you may try the following option to see if that helps.

Error 8004041d means QuickBooks/SDK rejected the automatic login: “This application is not allowed to log into this QuickBooks company data file automatically.” In practice, this commonly happens when a scheduled task runs in a different Windows session, under a different account, or without an interactive desktop - QuickBooks (and the QuickBooks SDK) require an interactive desktop session / approved integrated application certificate for the exact user/session that is doing the BeginSession.

QuickBooks and QuickBooks SDK are not designed to run as a service.
Someone should be logged in to the Windows user session.

Run Task only when user is logged on (Interactive session), Do not use "Run with highest privileges."

Edit the scheduled task → General tab → select Run only when user is logged on (not “Run whether user is logged on or not”).

Rationale: QuickBooks and the QuickBooks SDK require an interactive desktop. If the task is started in a non-interactive session (session 0) or as SYSTEM, it can’t establish a QuickBooks SDK BeginSession. Many users fix this by keeping a user logged into the server and setting the task to run under that same user.


Use the same Windows account that was used when authorizing QODB.C

The Integrated Application permission in QuickBooks is tied to the Windows user and the certificate. Make sure the scheduled task runs under the same Windows user account that you manually used when authorizing QODBC in QuickBooks. If they differ, re-authorize while logged in as the scheduled task user or change the task to run as the authorized user.



Confirm QODBC was allowed automatic login in QuickBooks Integrated Applications

In QuickBooks: Edit → Preferences → Integrated Applications → Company Preferences → find QODBC (or the exact application name shown during authorization) and ensure “Allow this application to log in automatically” is checked and the access level is appropriate (or explicitly select “Yes, always; allow access even if QuickBooks is not running” if available for your version). If you do not see the app, re-run the QODBC setup/support wizard and accept the certificate when QuickBooks prompts.


Make sure the QuickBooks company file is open, and QuickBooks is running in the interactive session.

For scheduled runs, quick test: log into the server interactively as the task user, open QuickBooks and the company file, then trigger the scheduled task manually (from Task Scheduler while still logged in) - if that works, but the scheduled run (when no interactive login) fails, it confirms the interactive-session issue.

Problem Description:

We’ve been having steady success with QODBC for a good while. We’re running QuickBooks on a VM and our custom application that queries it on another VM; both VMs are Server 2012.

All was well with our integration until I changed, by necessity, the setting for Enable 32-bit Applications. Once I made it True, the integration through QRemote did not work. QODBC Test Tool still works on the client just fine. It is a 32-bit app. I’m confused as to why our custom application worked fine when 32-bit was False, but not when 32-bit was True. I would have figured it was the other way around.

I looked at several articles on configuring QODBC to work with 64-bit applications, but that’s not exactly what we’re doing here. What is the most straightforward remedy to get our application with Enable 32-bit = True to work with the QRemote Server? I know the server is set up fine, as the QODBC Test Tool on the client works fine.

Solutions:

I guess you are using IIS.

When you set Enable 32-bit Applications = True, your IIS app pool runs as 32-bit.

You need to change the connection string to "QuickBooks Data QRemote."

When Enable 32-bit Applications = False, it will run as 64-bit.

You need to use the connection string as "QuickBooks Data 64-bit QRemote."

Note: The JDBC-ODBC bridge driver was removed in Java 8, preventing ODBC drivers from being usable in newer versions of Java or other Java-based applications.

Refer: Oracle JDBC-ODBC Bridge

How to Use QODBC with NetBeans

Problem Description:

QuickBooks Enterprise comes with a tool called QODBC that enables connecting to a QuickBooks database to read and write data. I have installed it and can successfully see QuickBooks data by connecting with Excel.

I am attempting to be able to read data in Talend Open Studio 5.4.1 by using the Generic ODBC connector. I can get a successful connection message when setting up the database connection, but retrieving the schema to see the tables shows no tables. There are no errors or any other indication - just no table listing.

Solutions:

Please query the table directly instead of loading tables. Use a tDBInput component, use a SELECT query, & Click on "Guess Schema."

For Example:

Select * from the customer

Problem Description:

We have a few stations where we utilize the read-only QODBC desktop version. On a station we just built, it keeps using the wrong QuickBooks user for the auto-login. I confirmed that the QuickBooks file is set to use the correct user for QODBC, and I also confirmed that our other stations are still connecting using the correct user; the issue is only with this one station.

QODBC seems to be otherwise working as expected. This isn't a usable state, however, as this station is reverting to a user with a different level of privileges on the system.

Solutions:

Please remove all the integrated applications via the following:

QuickBooks UI -> Edit -> Preferences -> Integrated Applications -> Company Preferences and reconnect QODBC again to see if it can solve the issue.

Please Refer:

How to remove QODBC Related Certificates from Integrated Application Under QuickBooks

Please Note: If QuickBooks is running and a user is logged in, the user specified in the Integration will be ignored, and the currently logged-in users on QuickBooks will be used.

When QuickBooks is not running, and you try to connect using QODBC auto-login, it will log in to QuickBooks with the user selected in the Integration settings in the QuickBooks file. But when QuickBooks is running, and you try to connect using QODBC auto-login, it will log in to QuickBooks with the user logged in to the QuickBooks file.

Problem Description:

I have a Mac operating system & I want to use QODBC on it. Is it possible to use QODBC on MAC?

I have a Linux Operating System & I want to use QODBC on it. Is it possible to use QODBC on Linux?

Solutions:

Yes, you can use QODBC on MAC or Linux. But you have to load some tools to use it. You can use Parallels or a similar program to allow Windows apps to run under Mac OS / Linux OS.

Or

You can install Windows alongside Mac OS/ Linux OS to run on the same machine. You can install Windows software on Linux or run Windows programs on a Chromebook. Virtual machines, dual-booting, and the Wine compatibility layer.

Please refer to the link below for more details:

5 Ways to Run Windows Software on a Mac

4+ Ways to Run Windows Software on Linux

Also, there are not many MAC apps that support ODBC as a data source, so you will need to use the Windows app for that purpose, but they can run on a Mac with the tools listed above.

Keywords: Apple, MacOS, Macintosh, AppleOS, macOS Mojave, MacBook, Mac OS X, Mac OS, macOS, Linux, Ubuntu, Linux Mint

For system requirement details of QODBC Online, click here.

How to install QODBC Online & Use Microsoft Excel/Access with QODBC

You can also see: How to use QODBC Online with QuickBooks Online Edition

For system requirement details of QODBC Online, click here.

Tags:

Installing QODBC Online

How to connect to QODBC Online

Tags: QuickBooks Online, QBO, MS Access, Excel, QODBC Online, connect online

Problem Description:

I want to upgrade my Operating System to Windows 10 and know if any precautions/actions are required for QODBC to keep working. 

Solutions:

Steps before upgrading to Windows 10:

Please follow the steps below before upgrading the Operating System to Windows 10.

1) Deactivate the QODBC license with the CDKEY from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >> Go To "System DSN" Tab >> select QuickBooks Data >> click "configure" >> switch to activate/deactivate >> click "deactivate"

Please refer to the link below to Deactivate the QODBC license.

How to activate/deactivate QODBC

It is highly recommended that you deactivate the license before upgrading the OS.

2) Uninstall QODBC from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Uninstall QODBC

Follow unthe install steps & uninstall QODBC.

3) Upgrade the OS to Windows 10.

4) After upgrading the OS to Windows 10, please refer to the link below for installing QODBC and follow the steps:

Connecting QODBC Driver to QuickBooks for the First Time (Video)

5) After the successful installation of QODBC, please activate the QODBC license with the CDKey from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >> Go To "System DSN" Tab >> select QuickBooks Data >> click "configure" >> switch to activate/deactivate >> click "activate"

Please refer to the link below to activate the QODBC license.

How to activate/deactivate QODBC

Problem Description:

I have upgraded my system to Windows 10 and am facing licensing issues after upgrading the OS. I have a QODBC license, but my QODBC Setup Screen >> About tab says Evaluation Version has expired. 

Please help me with this issue.

Solutions:

Steps after upgrading to Windows 10:

If you did not deactivate the license and have already upgraded Windows directly and are unable to use QODBC, then please follow these steps:

1) Try to run the QODBC Setup Screen as "Run as Administrator" from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Right-click on QODBC Setup Screen and "Run as Administrator."

If the above does not resolve the issue, then please follow the steps below:

2) Please try to deactivate the license with the CDKEY from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >> Go To "System DSN" Tab >> select QuickBooks Data >> click "configure" >> switch to activate/deactivate >> click "deactivate"

3) Please try to activate QODBC with the CDKEY from:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >> Go To "System DSN" Tab >> select QuickBooks Data >> click "configure" >> switch to activate/deactivate >> click "activate"

Please activate with the CDKEY. After the successful activation, please test the connection with QuickBooks using the QODBC Test Tool.

Please refer to the link below to activate/deactivate the QODBC license.

How to activate/deactivate QODBC

Using the latest version of QODBC, credit for deactivation CDKEY is received instantly.

If you encounter a "CDKEY Exhausted" message, wait 24-48 hours and then try to activate the license.

If you are still facing licensing issues or cannot deactivate QODBC, raise a support ticket with "Sales - Registration - Activation Department."

Click Here to raise a support ticket.

Problem Description:

I have a question about setting ODBC to auto-login. I am trying to automate some tasks and wanted to auto-login. We have two different company files for accounting purposes. If I set the path in the odbc to the company file, how do I change this to access the second company?

Solutions:

There is a limitation with the QuickBooks SDK: it can connect to only one company file simultaneously on a machine. QODBC uses QuickBooks SDK & QRemoteServer uses QODBC. Thus, you can open one company file at a time on a device.

You can create multiple DSNs pointing to different company files and use this DSN in your configuration.

Please refer to the steps below for creating multiple DSNs pointing to different company files.

1) Create a new DSN.

For example, you have a Company file "A," and let us create a DSN for Company "A" with the DSN name "CompA." Please refer to the article mentioned below for creating DSN:

How to make or configure a QODBC DSN

2) Set up auto login to QuickBooks using QODBC.

Please refer to the article mentioned below for configuring auto-login to QuickBooks using QODBC.

How to set up QODBC Driver to auto-connect to QuickBooks (Video).

How to set up QODBC for auto-login into QuickBooks.

Let us repeat steps 1 & 2 for the Company file "B."

1) Create a new DSN.

Create DSN for Company "B" with DSN name "CompB." Please refer to the article mentioned below for creating DSN:

How to make or configure a QODBC DSN

2) Set up auto login to QuickBooks using QODBC.

Please refer to the article mentioned below for configuring auto-login to QuickBooks using QODBC.

How to set up QODBC Driver to auto-connect to QuickBooks (Video).

How to set up QODBC for auto-login into QuickBooks.

Use DSN in Applications:

We have created multiple DSNs. Now we use it in our application.

In this example, I am using DSN in VBA code. Please refer to the sample code for using multiple DSNs in VBA through QODBC:

Public Sub Test()

Const adopt static = 3

Const adLockOptimistic = 3

Dim oConnection

Dim sConnectString

sConnectString = "DSN=CompA;OLE DB Services=-2;"

// Write your query here as per your requirements. //

Set oConnection = CreateObject("ADODB.Connection")

oConnection.Open sConnectString

oConnection.Close

Set oConnection = Nothing

Sleep(10)

sConnectString = "DSN=CompB;OLE DB Services=-2;"

// Write your query here as per your requirements. //

Set oConnection = CreateObject("ADODB.Connection")

oConnection.Open sConnectString

oConnection.Close

Set oConnection = Nothing

Sleep(10)

End Sub

Keywords: QB Win Log with multiple companies, log in with multiple companies 

Problem Description 1:

We are adding invoice records to QuickBooks using an Access front end. When we create the records and try to insert them into QuickBooks, the line items seem to go, but when the invoice header is inserted, we get an error that the Child Record must be inserted before the Header Record in BuildXMLHeader. I have examined the data being passed, and it all looks correct.

Problem Description 2:

I upgraded my QuickBooks Premier Plus Professional Services to 2016 (from 2014). I skipped updating to 2015.

I installed the new QODBC connector, but I cannot connect to my Access database. I have tried to uninstall the MS Access Database driver, but I get the error message ODBC call failed- Error 10004.

Problem Description 3:

I just updated QuickBooks Enterprise 14 to Enterprise 23. Using an Access database 2013 32-bit. I get an error when trying to process a Packing list in Access to invoice in QuickBooks.

I'm having an issue with my database sending a packing list to QuickBooks. It's working, and then it stops.

"ODBC--call failed".
 

Problem Description 4:

I have an MS Access database containing QuickBooks Data as the linked table. Recently, I changed my Optimizer file path & after changing the Optimizer path, I am facing a slow performance issue.

How can I solve this issue? 

Solutions: 

You need to re-link the MS Access-linked table to resolve the issue. Delete the old linked table & re-link it.

After changing the optimizer file path, you need to re-link the linked table in MS Access because your MS Access Linked table contains an old Optimizer file path.

Please note: Linked Table Manager in MS Access will not update the Optimizer file path; you need to re-link the linked table in MS Access to solve this issue.

The solution to this issue is to re-create the linked table.

Open MS Access Linked Table:

Right-click on the On Your Linked Table:

Now, click on the Delete.

Now Link the Same Table. After linking the table, you will get the updated optimizer file path.

To view the Optimizer file path & other table properties, hover your mouse over the table name so that you can view table properties.

Please keep QuickBooks running, log in as Admin to your company file, and try to connect again with MS Access.

Please refer to the link below for How to Create a Linked Table in MS Access:

How to Use QODBC with Microsoft Access 2007

How to Use QODBC with Microsoft Access 2010

If the above does not resolve the issue, please download the latest QODBC version.

QODBC Download

Skip the CDKEY Step during installation. Restart the Machine after a new version is installed (if prompted)

If the Above Solutions don't work, please post a ticket to us, and we will further investigate your issue.

Tags: Re-link linked tables, Re-link table, Re-add table, Re-Add linked tables, Refresh Linked tables, ODBC-Connection to 'QuickBooks Data' failed, #Deleted,[#Deleted], ODBC--call failed, call failed, #Deleted

Problem Description:

How to record the issue I am facing and show/share the screen.

Solutions:

Please follow the steps below for recording the issue you are facing.

1) Download screen recorder "TinyTake."

Click Here to Download TinyTake.

Download the software & install it.

2) Run TinyTake from the Start menu.



3) Click on Capture Video.



3) Please select the region you want to show & click on Start Recording.





4) Click on the stop to finish recording. You can click on pause to pause recording.



4) Click on the save icon to save the video locally. Click on Save & Share to upload the video to TinyTake's video sharing service.

5) Copy the TinyTake video link by clicking on the "Copy Link" button and share it with us in a support ticket.

Problem Description:

How can I identify if the application is 32-bit or 64-bit?

Solutions: 

SQL Server

If your application is SQL Server, you can identify it by starting your "SQL Server Management Studio."

Log in to your SQL Server.

On the left-hand side panel, you will find the Serve. Right-click on the "SQL Server" and Select Properties.



If SQL Server is 32-bit, you will notice 32-bit or x86 in the product info.



If SQL Server is 64-bit, you will notice 64-bit in the product info.

MS Office

If your application is MS Access or MS Excel, you can identify it from the Help menu in MS Access/MS Excel.

Using the DSN list window

You can verify the application from the DSN list window, also.

If your application shows the QODBC DSN below at the time of connection, then your application is 32-bit.

QuickBooks Data, QuickBooks Data QRemote

If your application shows the QODBC POS DSN below at the time of connection, then your application is 32-bit.

QuickBooks POS Data, QuickBooks POS Data QRemote

If your application shows the QODBC Online DSN below at the time of connection, then your application is 32-bit.

QuickBooks Online Data, QuickBooks Online Data QRemote



If your application shows the QODBC DSN below at the time of connection, then your application is 64-bit.

QuickBooks Data 64-bit QRemote

If your application shows the QODBC POS DSN at the time of connection, then your application is 32-bit.

QuickBooks POS Data 64-bit

If your application shows the QODBC Online DSN at the time of connection, then your application is 32-bit.

QuickBooks Online Data 64-bit

Using Task Manager

You can verify the application from the Task Manager window, also.

If the application is 32-bit, you will notice *32 after the EXE name in the process tab. If you can't see *32 after the EXE name, the application is 64-bit.

                                               

Tags: QuickBooks Online, QBO, SQL Server online, QODBC Online

To use QODBC Online with Jitterbit Community Edition 3.0.0, you should follow the steps below to configure your QODBC Online driver and Jitterbit connection. These steps work for QODBC with Jitterbit 3.0.0 on 32-bit Windows 7. Other platforms have not been tested.

First, you need to configure QRemote. To configure QRemote, please follow the steps below:

QRemote has two components: "QRemote Client Driver for QODBC Online" and "QRemote Server for QODBC Online." 

QRemote Client Driver: Allows service-based applications and 64-bita pplications to connect to the QRemote Server and send the request to the QRemote Server for processing. 

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

Start "QRemote Server for QODBC Online" from the start menu. ( If QRemoteServer is not running ) 

Double-click the QRemote Server icon from the system tray

QRemote Server Main screen shows the IP address and port, allowing the QRemote Client to connect.

Note the IP address and Port number listed on the QRemote Server "Event Logs window.

Create a new DSN entry/or configure the existing one

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

Configure QODBC Online Data Source

"QuickBooks Online Data QRemote" is the default DSN created when installing QODBC.

Configure the DSN and provide the IP address and Port as listed under "QRemote Server."

Under the QRemote for QuickBooks Online– 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: Keep default key "QODBC#QRemote$1" (In case you want to use encrypted data transfer between QRemote client and QRemoteServer, you can configure your encryption key on QRemoteServer and use the same on QRemote Client DSN) 

• Remote DSN: select the QODBC Online DSN "QuickBooks Online Data" from the list. ( Make sure QRemote Server is running) 

After configuring QODBC, you need to configure Jitterbit. To configure Jitterbit, please follow the steps below:

1. Start the Jitterbit client

2. Right-click Sources and create a New Source

3. Type QuickBooks ONLINE in the Name field

4. Select the Database for the type

5. Click Options

6. Ensure the box marked "Construct connection string manually" has a tick in it

7. Enter DSN=QuickBooks Online Data QRemote into the field adjacent to the checkbox.

8. Click the Save icon.

Tags: QuickBooks Online, QBO, Jitterbit, QODBC Online

To use QODBC POS with Jitterbit Community Edition 3.0.0, you should follow the steps below to configure your QODBC POS driver and Jitterbit connection. These steps work for QODBC with Jitterbit 3.0.0 on 32-bit Windows 7. Other platforms have not been tested.

First, you need to configure QRemote. To configure QRemote, please follow the steps below:

QRemote has two components: "QRemote Client Driver for QODBC POS" and "QRemote Server for QODBC POS." 

QRemote Client Driver: Allows service-based applications and 64-bita pplications to connect to the QRemote Server and send the request to the QRemote Server for processing. 

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

Start "QRemote Server for QODBC POS" from the start menu. ( If QRemoteServer is not running ) 

Double-click the QRemote Server icon from the system tray

QRemote Server Main screen shows the IP address and port, allowing the QRemote Client to connect.

Note the IP address and Port number listed on the QRemote Server "Event Logs " window

Create a new DSN entry/or configure the existing one

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

Configure QODBC POS Data Source

"QuickBooks POS Data QRemote" is the default DSN created when installing QODBC.

Configure the DSN and provide the IP address and Port as listed under "QRemote Server."

Under the QRemote for QuickBooks POS– 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 :   

    (Keep Encryption Key empty/blank. In case you want to use encrypted data transfer between QRemote client and QRemoteServer, you can configure your encryption key on QRemoteServer and use the same on QRemote Client DSN) 

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

After configuring QODBC, you need to configure Jitterbit. To configure Jitterbit, please follow the steps below:

1. Start the Jitterbit client

2. Right-click Sources and create a New Source

3. Type QBPOS in the Name field

4. Select the Database for the type

5. Click Options

6. Ensure the box marked "Construct connection string manually" has a tick in it

7. Enter DSN=QuickBooks POS Data QRemote into the field adjacent to the checkbox.

8. Click the Save icon.

To use QODBC with Jitterbit Community Edition 3.0.0, you should follow the steps below to configure your QODBC driver and Jitterbit connection. These steps work for QODBC with Jitterbit 3.0.0 on 32-bit Windows 7. Other platforms have not been tested.

First, you need to configure QRemote. To configure QRemote, please follow the steps below:

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

QRemote Client Driver: Allows service-based applications and 64-bita pplications to connect to the QRemote Server and send the request to the QRemote Server for processing. 

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

Start "QRemote Server for QODBC" from the start menu. ( If QRemoteServer is not running ) 

Double-click the QRemote Server icon from the system tray

QRemote Server Main screen shows the IP address and port, allowing the QRemote Client to connect.

Note the IP address and Port number listed on the QRemote Server "Event Logs " window

Create a new DSN entry/or configure the existing one

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

Configure QODBC Data Source

"QuickBooks Data QRemote" is the default DSN created when installing QODBC.

Configure the DSN and provide the IP address and Port as listed under "QRemote Server."

Under the QRemote for QuickBooks – 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: Keep default key "QODBC#QRemote$1" (In case you want to use encrypted data transfer between QRemote client and QRemoteServer, you can configure your encryption key on QRemoteServer and use the same on QRemote Client DSN) 

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

After configuring QODBC, you need to configure Jitterbit. To configure Jitterbit, please follow the steps below:

1. Start the Jitterbit client

2. Right-click Sources and create a New Source

3. Type QuickBooks in the Name field

4. Select the Database for the type

5. Click Options

6. Ensure the box marked "Construct connection string manually" has a tick in it

7. Enter DSN=QuickBooks Data QRemote into the field adjacent to the checkbox.

8. Click the Save icon.

Create a New Workspace

     Start Alpha Five and create a new workspace. It could be called Online. adb - a holder for the entire application.

     Click the Workspace & Tasks tab -> Click -> choose to Create a new, empty Workspace -> click OK.

Data Source Setup

     First, click on Data Source, and choose the New Active-Link Table... option.

Select the Single/Multiple Active Link table as per your requirement.

Build a connection string by clicking the Build button.

Select connection type "ODBC," Data Source Name "QuickBooks Online Data," Vendor "ODBC, & click on the Test Connection button.

Click the "Connect" button to connect to QuickBooks Online.

Now that we are connected, click"Next" to proceed to the next step.

Select the tables that you want & click "Next" to proceed to the next step.

Active link creation is in process.

An active link is created.

Click on the table to view data.

Tags: QuickBooks Online, QBO, Alpha Five, QODBC Online

Problem Description:

I downloaded the trial version of your driver this morning and am excited about the prospects. I've installed it and can get the fields and tables to appear in QODBC Test Tool, but I cannot connect using FileMaker Pro. 

Solutions:

Please follow the steps below for FileMaker connectivity using QODBC Online.

1) Open FileMaker Pro & click on the Browse button.

2) Please select the ODBC data source.

 

3) Please select the ODBC data source "QuickBooks Online Data" & click on the "Continue" button.

For FileMaker 64-Bit, please select "QuickBooks Online Data 64-Bit QRemote."

4) Please enter the username & password for the ODBC data source. If you have not defined any username & password, then click on the "OK" button.  

 

5) Select tables & columns that you want to use, then please click on the "Insert into SQL Query" & "Execute" buttons.

6) Save results & you can see results.

Tags: QuickBooks Online, QBO, FileMaker, QODBC Online

To use QlikView with QODBC Online,  please follow the steps below.

1. Open QlikView & Create the new file.

2. Select Data Source. Click on Browse.

3. Please select the MS Excel file & click "Next."

4. Click "Next."

5. Save the QlikView file & click "Next."

6. Select chart type & Click "Next."

7. Define dimensions & list boxes & click "Next".

8. Add expression & Click Finish

9. Now, please navigate to the file & click on Edit Script.

10. Please select the ODBC database & enable the "Force 32 Bit" option & click on Connect.

11. Select "QuickBooks Online Data" DSN & click on Test Connection.

We can see the connection made with QuickBooks Online through QuickBooks Online Data DSN.

12. QlikView locks up when we click the "Select" button on the Edit Script window. Please do not click on the Select button. You can write SQL statements as per your requirement & click on the "Reload" button to execute the script.

For Example
SQL select * from the customer

13. Choose a field that you want to show from the tables that are returned by SQL statements & click on OK.

You can see the results. You can repeat the same process for other tables & fields.

Note: In case the QlikView designer is hanging when using "Select * from TableName," Please try changing the SQL Statement to include limited Fields, e.g., "Select ListID, Name from Customer."

Tags: QuickBooks Online, QBO, Qlikview, QODBC Online

Problem Description:

I can't configure QuickBooks Data DSN from the Configure QODBC Data Source window. When I click on QuickBooks Data, Configure is grayed out.

Please let me know what I am doing wrong.

Problem Description:

I don't seem to have the Configure QODBC Data Source or the Configure QODBC Data Source 64-Bit programs under the QODBC Driver for use with QuickBooks.

Solutions:

You have opened a 64-bit ODBC manager. On 64-bit platforms, 32-bit ODBC drivers are available to 32-bit applications but not 64-bit. What determines which ODBC driver architecture is used, whether your application is 32-bit or 64-bit, not whether your client platform (or database platform or DBMS) is 32-bit or 64-bit. Since QODBC is a 32-bit-only ODBC driver, the only applications that can access it are 32-bit applications. So if you open the ODBC Data Source window by default, it will open the 64-bit ODBC Data Source Manager because the OS is 64-bit.

You need to search for "Configure QODBC Data Source."

OR 

OR 

Or

Run the 32-bit ODBC admin utility to see the data source:

C:\windows\sysWOW64\odbcad32.exe

For the 64-bit ODBC admin utility to see the data source:

c:\WINDOWS\System32\odbcad32.exe

Open Configure QODBC Data Source>>Go To "System DSN" Tab>> select QuickBooks Data>> click "configure"

Start>> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >>Go To "System DSN" Tab >> select DSN name >> click "configure">> General tab >> select mode when opening "Same as company file" option.

Problem Description:

I have an inventory control system (C #, SQL Server) that needs read-only access to four tables in the accounting system. I have deployed your multiuser version and can access the local QuickBooks instance from your VB app, Excel, and my app.

1. When I run your VB app in the production RDP session, the ODBC behavior is as expected.

2. I created a WPF/c# app to duplicate your VB and ran it in the production RDP session. The ODBC's behavior is expected.

3. When I run my app in my development environment, the ODBC behavior is as expected.

4. When I run my app in the production RDP session, opening the ODBC connection takes > 6 minutes. But it opens.

Please let me know what I am doing wrong.

Solutions:

Please reset your Optimizer file, check the connection time, and log the connection time in your application. Please refer:

How to Remove Optimizer file

Please try the below .net application below for the troubleshooting of the time delay in connection opening and querying:

Sample code for Troubleshooting Connection Time Issue

If the above does not resolve the issue, please change the application, as it could eat more environmental resources.

Also, please try to move the process of reading the QuickBooks tables to a background task. It will solve the problem. I suspect that your app is consuming most of the thread pool. Creating an explicit task provides sufficient resources to resolve the issue.  

Problem Description 1:

I have tested using the QODBC Test Tool and the QRemote DSN test connection. I cannot connect to the QRemote DSN. I am getting the following error:

Problem Description 2:

I am trying to connect to the QRemote Server from my application. The code below hangs on the .open command:

Dim cnQODBC As New System.Data.Odbc.OdbcConnection("DSN=QuickBooks Data 64-bit QRemote;OLE DB Services=-2;")

Dim daQODBC As System.Data.Odbc.OdbcDataAdapter = New Odbc.OdbcDataAdapter() cnQODBC.Open()

The QODBC server does not show any activity. 

Solutions:

Please follow the steps below to resolve the issue.

You will get the message "Could not connect to server" or "Could not connect to QRemoteserver" error due to one of the following reasons:

1) QRemote Server is not running.

2) IP/Port in the QRemote client differs from the QRemote Server.

3) If you are connecting remotely, then there might be a firewall blocking the connection.

Please ensure the Version of QRemote on the Client machine is the same as QRemote on the Server Machine. Please make sure your firewall allows communication to the IP address of QRemoteServer, check if you are using the correct IP address of the remote machine, and also, please make sure QRemote is bound to the same IP address you are using. Also, try restarting the machine.

4)  Please ensure the Version of QRemote on the Client machine is the same as the version of QRemote on the Server Machine.

For Example:

If the client machine QRemote version is 24.0.0.361, then the server machine QRemote version should also be the same version i.e., 24.0.0.361
If the QRemote versions on both machines differ, please make them the same by installing the same QODBC version.

You can get the latest QODBC version from the link below:
QODBC Driver for QuickBooks Download

5) Please verify QRemote is configured correctly.

For 32-bit QRemote DSN:

Start>> All Programs>>QODBC Driver for use with QuickBooks >> Configure QODBC Data Source >>Go To "System DSN" Tab >> select QuickBooks Data QRemote >> click "configure":

Please verify IP & Port from QRemote Client. It should be the same as it is on the QRemote Server. You can find the QRemote Server running in the System Tray.

If it is not running, then please run the following:

Start>>All Programs>> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

Please verify "Remote DSN" and select "QuickBooks Data "DSN from the dropdown >> click "Test Connection."

For 64-bit QRemote DSN:

Please verify your QRemote DSN configuration:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> Configure QODBC Data Source 64-bit >> Go To "System DSN" Tab >> select QuickBooks Data 64-bit QRemote >> click "configure":

Please verify IP & Port from QRemote Client. It should be the same as it is on the QRemote Server. You can find the QRemote Server running in the System Tray. If it is not running, then please run the following:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

If it is not running, then please run the following:

Start >> All Programs >> QODBC Driver for use with QuickBooks >> QRemote Server for QODBC

Please verify "Remote DSN" and select "QuickBooks Data "DSN from the dropdown >> click "Test Connection."

Problem:

I am getting an error "11118 - System License Error."

I am getting an error "11119 - RegFile1 License Open Error"

I am getting an error "11120 - RegFile1 License Error"

I am getting an error "11121 - RegFile2 License Open Error"

I am getting an error "11122 - RegFile2 License Error" 

I am getting an error "unable to open license"

Cause:

11118 - System License Error:

11118 - System License Error could be due to one of the following reasons:

1) The license file is missing or corrupted.
2) You don't have sufficient permission to access the License file.
3) The license file has been changed.

11119 - RegFile1 License Open Error:

11119 - RegFile1 License Open Error could be due to one of the following reasons:

1) The license file is missing or corrupted. 
2) You don't have sufficient permission to access the License file.
3) The license file has been changed.

11120 - RegFile1 License Error: