The first query takes ages
How you'll know: A query on a big table, transaction lines especially, runs for minutes.
Fix: That's the QODBC Optimizer building its local cache. The first pass reads every record, and later ones fetch only what changed. Let it finish once, and filter by date rather than pulling every year.
Balances that lag behind QuickBooks
How you'll know: An account balance or on-hand quantity doesn't match what QuickBooks shows right now.
Fix: The Optimizer cache lives on one computer, so other users' latest changes may not be in it yet. Its setting for balances and quantities has a real-time mode: slower, but current.
Power BI or 64-bit Excel can't find the data source
How you'll know: The QuickBooks DSN doesn't appear in the list, or the connection fails straight away.
Fix: A 32-bit versus 64-bit mismatch. Use the 64-bit driver that ships with recent QODBC versions, or QRemote to bridge a 64-bit program to an older 32-bit install.
Works at your desk, fails on a schedule
How you'll know: A refresh runs fine by hand but fails from SQL Server, a web server or a scheduled service.
Fix: QuickBooks can't run as a Windows service, so FLEXquarters says service-based programs need QRemote to reach it. Plan any unattended refresh around that from the start.
Writes that fail or half-apply
How you'll know: An insert into an invoice or item table errors out, or lands with fields missing.
Fix: Writing needs the read/write edition, and even then some data is off-limits. For regular write-back, the SDK or Web Connector is the steadier route.