FAQ for QuNect ODBC for QuickBase

Troubleshooting

"I get an error message like this: [QuNect][QuickBase]A connection with the server could not be established 12029".

Please read Getting Started

Security

How secure is QuNect ODBC for QuickBase?

Please read QuNect Security

Purchasing

Which QuNect ODBC for QuickBase product in the Windows family do I need to purchase?

The first step is to determine what kind of Windows operating system you have. If you are running Windows XP, Vista, 7, 8 or 10 then you're running a desktop operating system and you need to purchase QuNect ODBC for QuickBase 2016 (32 and 64 bit).

If you are running Windows Server 2000, 2003, 2008, 2012, 2016 etc. then you're running a server operating system and you need to purchase QuNect ODBC for QuickBase 2016 (32 and 64 bit server).

How do I get updated versions of QuNect ODBC for QuickBase

The latest version of QuNect ODBC for QuickBase is always available at http://www.qunect.com. Since licensing is done online you can download and install the latest version at any time without having to worry about entering license keys. When the first of the year rolls around QuNect releases a new product version of QuNect ODBC for QuickBase for that year. Customers who have purchased their license within 6 months of the release of the new product can upgrade to the new product for free by contacting support. All other customers can upgrade to the new product by paying 40% of the full price for a license. Please contact support to receive an invoice for your upgrade.

Versions

How do I tell what version of QuNect ODBC for QuickBase I have installed?

Start->All Programs->QuNect ODBC for QuickBase->32 Bit ODBC Admin->Drivers (tab)->Version (column) If you're on a 64 bit machine then you'll need to also do Start->All Programs->QuNect ODBC for QuickBase->64 Bit ODBC Admin->Drivers (tab)->Version (column)

How do I interpret the version number of QuNect ODBC for QuickBase?

QuNect ODBC for QuickBase version numbers start with either a three or a six for 32 bit or 64 bit respectively. After the first period, the two digit year follows. The remaining numbers just document the particular point release. So the scheme is like this:

for 32 bit

3.YY.NN.NN

for 64 bit

6.YY.NN.NN

Where YY is the two digit year and the NN.NN is the point release.

How do I tell what versions of QuNect ODBC for QuickBase I have paid and trial licenses for?

First make sure you are logged in to QuickBase as the user who the license is attributed to and then click on this link. Then follow the directions on the page.

Compatablity

What version of ODBC does QuNect ODBC for QuickBase support?

ODBC version 3.0 is supported (Level 2 API)

What operating systems does QuNect ODBC for QuickBase support?

Windows XP Home and Professional, Windows 2000, Windows Vista, Windows Server 2003, Windows Server 2008, Windows 7

What hardware does QuNect ODBC for QuickBase support?

All x86, x64 based Intel and AMD processors as well as Sun SPARC processors

In MS Access I can see my list of tables but I can't link to a table

Make sure you have the same application token installed in your QuickBase application and in your QuNect ODBC for QuickBase DSN. Please watch Getting Started

SQL Syntax

What characters are wildcard characters in a LIKE clause?

% (percent sign) means any number of characters and _ (underscore) means any single character.

What SQL JOINs does QuNect ODBC for QuickBase support?

INNER JOIN and LEFT OUTER JOIN but not RIGHT OUTER JOIN

What SQL grammar is supported?

minimum+ SQL grammar

How do I specify dates?

SELECT * FROM tablename WHERE datefield = {d '2008-04-25'}

How do I specify timestamps?

SELECT * FROM tablename WHERE timestampfield = {ts '2008-04-25 10:19:48.529'}

How do I specify time?

SELECT * FROM tablename WHERE timefield = {t '10:19:48'}

QuickBase Fields

Why do QuickBase user fields enclose names in double quotes?

Please read QuickBase User Field Behaviour

How do I control the truncation of QuickBase text fields?

Text fields are truncated by QuNect ODBC for QuickBase. If it's a single line text field (QuickBase field property Number of lines is set to one) then it's truncated to 255 characters. If it's a multi-line text field then (QuickBase field property Number of lines is greater than one) it's truncated to 65535 characters. But if you've set the Max characters property of the QuickBase field then it will be truncated to that length or to 65535 characters, whichever is the smaller number.

Why can't I use FIDs to refer to field names within SQL Server when I use the four part name syntax. When I use OPENQUERY in SQL Server I can refer to a field by it's name or by its field identifier?

That's as designed. If you want to use FIDs with four part names you'll need to use a DSN with the checkbox checked that's labeled "Use field identifiers as field labels". But then you can't use the field names with four part names. This is a SQL Server limitation. When you talk to QuNect ODBC for QuickBase directly, as with OPENQUERY, it knows to consider both possibilities for field names. However SQL Server asks QuNect ODBC for a list of field names for each table in a SQL statement before it sends the SQL to QuNect ODBC for QuickBase. Then it verifies that each field in the SQL is valid. Since QuNect ODBC for QuickBase can present only one field name to SQL Server when it asks there is no possibility for matching either on field name or field identifier. It's one or the other.