[QODBC-Desktop] - QODBC QRemote Multi-Company File Setup
Problem Description:
QODBC users need to configure QRemote to switch between multiple QuickBooks company files on the same or different machines. The QRemote Server connects to whichever company file is currently open in QuickBooks, and clients connect to the QRemote Server to access data. Customers may need to set up separate DSNs for each company file, or automate company file switching for workflows that require access to multiple files.
Affected products: QODBC Desktop (all versions), QRemote Server/Client, QuickBooks Desktop (Enterprise, Pro, Premier), Microsoft Excel, Microsoft Access, SQL Server linked tables Expected outcome: QRemote is properly configured to switch between company files; QRemote Server and Clients are using matching port and DSN configurations; queries execute successfully in the desired company file.
Symptoms:
- QRemote Test Tool connects successfully, but queries access the wrong company file.
- QRemote Server tray icon does not update when the company file changes in QuickBooks.
- Client applications cannot connect to a specific company file, or repeatedly prompt for a certificate.
- Only one company file is accessible at a time via QRemote, and switching requires manual reconfiguration.
- Customers with a single QODBC license on a machine needing to access multiple company files under different Windows users.
Cause:
QRemote licensing and configuration are managed at the machine level. The QRemote Server listens on a specific port and connects to the QuickBooks company file currently open in the QuickBooks session. Each QRemote Client DSN connects to the QRemote Server using the configured port and DSN name. To access multiple company files, either:
- One license per machine is sufficient (one QODBC license allows all company files on that machine), with separate DSNs labeled for each company.
- Multiple Windows users on the same machine, each with their own QuickBooks and QODBC installation, can each access their designated company file.
- QRemote Server can be shared across companies on the same machine, with each company having its own DSN pointing to the server.
Solution:
- Configure QRemote Server port settings. On the QuickBooks host machine (Server Side), ensure QuickBooks is running with only one company file open at a time. Launch QRemote Server (accessible via the system tray or Start → All Programs → QODBC Driver for QuickBooks → QRemote Server). Note the port number configured in the QRemote Server settings (File → Settings → Advanced Tab). The default port is 8383. Record this number.
- Configure QRemote Client DSNs for each company file. On each client machine, create a System DSN for each QuickBooks company file using Start → All Programs → QODBC Driver for QuickBooks → Configure 32-Bit QODBC Driver → System DSN → QuickBooks Data QRemote → Configure. Enter a descriptive name for each DSN (e.g., "QuickBooks Data QRemote - Company A", "QuickBooks Data QRemote - Company B"). Ensure each DSN uses the same port number as the QRemote Server.
- Label DSNs for organizational clarity. Assign each QRemote DSN a name that corresponds to the associated QuickBooks company file. This makes it easy to select the correct DSN when switching between files.
- Switch company files in QuickBooks. To switch the company file that QRemote accesses:
- Close the currently open company file in QuickBooks.
- Open the second company file you want to work with in QuickBooks.
- Wait a few seconds for the QRemote Server to detect the new file (you should see the file name update in the QRemote Server tray icon tooltip or window).
- In the client application (Excel, Access, or other ODBC-consuming application), select the QRemote DSN that corresponds to the newly opened company file.
- Optional: Automate company file switching. If you frequently switch between company files, consider:
- Using command-line automation or Task Scheduler to open the appropriate QuickBooks file before querying via ODBC.
- Running separate Windows users via Remote Desktop or VM with QuickBooks open in each session, each dedicated to a company file.
- Creating a batch script that runs PowerShell scripts to configure each DSN and open the corresponding company file.
- Verify the QRemote About screen. The About screen should display the license status.
- Test your queries. Open the affected workbook (Excel) or database (Access) and attempt your standard QODBC queries against the selected company file. All queries should execute without error.
SQL Examples:
After applying the resolution steps above, any standard QODBC query will work through the 32-Bit or 64-Bit DSN connections:
SELECT ListID, FullName FROM Customer WHERE IsActive = True
SELECT * FROM Invoice WHERE TxnDate >= {d'2025-01-01'}
Example Scenarios:
Scenario 1 - Single machine, multiple company files:
A customer with a single QODBC read-write license on one Windows machine needed to access two different QuickBooks company files. The customer created two QRemote DSNs (one for each company file), both pointing to the same QRemote Server port. To switch between files, the customer closed the current QuickBooks company file and opened the desired one, then selected the corresponding DSN in the client application. The QODBC About screen correctly displayed the active company file name.
Scenario 2 - Multiple Windows users on one machine:
A customer with two QuickBooks company files on a single machine needed separate users to access each file independently. The customer created two Windows user accounts, each with its own QODBC installation and QRemote Server configuration. Each user selected their designated DSN in the client application. Since licensing is per-machine, one QODBC license sufficed for both users, as only one QuickBooks instance is active at a time.
Additional Notes:
- Single license, dual activation: One CDKEY activates both the 32-Bit and 64-Bit QODBC drivers simultaneously. There is no separate 64-Bit license or CDKEY. Activation is managed through the 32-Bit ODBC Administrator (
odbcad32.exe located at C:\Windows\SysWOW64\odbcad32.exe on 64-Bit Windows).
- Subscription renewal sync: After any subscription renewal, payment method change, or account update on QODBC's end, the license may need to be synced again through the 32-Bit ODBC Administrator. Clicking the Sync Now button on the Activate/Deactivate tab refreshes the server-side status.
- QRemote conflicts: QRemote is a background service that maintains persistent connections to QuickBooks. If QRemote is running when you attempt to activate or sync your license, it may prevent the activation from completing. Always close QRemote before attempting license activation or sync.
- Differentiating between 32-Bit and 64-Bit ODBC: On a 64-bit Windows system, there are two separate ODBC Administrators. The 32-Bit version is located at
C:\Windows\SysWOW64\odbcad32.exe. The 64-Bit version is at C:\Windows\System32\odbcad32.exe. Always use the 32-Bit version for QODBC activation and configuration.
- Trial version consideration: If QuickBooks or QODBC are in trial mode, the trial license may take precedence over a purchased read-write subscription in some contexts. Ensure that trial modes are fully licensed before troubleshooting read-write connectivity issues.
- Power BI Gateway - ODBC Compatibility: When connecting to Power BI (On-Premises Data Gateway), set the QODBC/QRemote ODBC compatibility mode to 3.8. This applies to all QODBC and QRemote DSNs (32-Bit, 64-Bit, QuickBooks Data, QuickBooks Data QRemote). Without this setting, Power BI reports may fail to refresh.
Related Articles:
QODBC 64-Bit Driver Activation Through 32-Bit ODBC AdministratorHow to Activate QODBCQODBC Subscription License Broken After QODBC 24 UpgradeUnderstanding 32-Bit vs 64-Bit ODBC Drivers on WindowsHow to remove QODBC Related Certificates from Integrated Applications under QuickBooksQODBC Online - Configuring Multi-User Terminal Server Connections and Running a Daily Optimizer Script
Keywords:
QODBC QRemote Multi-Company Company File DSN Port Configuration Activate/Deactivate 32-Bit ODBC 64-Bit ODBC QuickBooks Admin System DSN License Per-Machine Windows User
Support Tickets: SRW-959-90808, OSX-940-76342
|