3.10.03.78
This is the last release of the 2010 version of QuNect ODBC for QuickBase.

3.10.03.38
SELECT TOP now works with SQLExtendedFetch

3.10.03.39
SQLFetchScroll now works with an array of rows and with SQL_FETCH_ABSOLUTE this is important when doing a DELETE in SQL Server with a four part name and a WHERE clause.

3.10.03.40
When connecting to SQL Server text fields can go as large as 65536.

3.10.03.42
Now any error connecting to the license table will cause an error on connection.

3.10.03.43
Made QuNect behave the same way for MSQuery and MS Access.

3.10.03.44
Using cbTableName in SQLSpecialColumns.

3.10.03.45
String literals are now at 65535 in length double what they were before. Also you can do a select and see application variables.

3.10.03.46
Changed the MAX_IDENTIFIER_LEN in INFO.CPP to 255 from MAX_TOKEN_LEN

3.10.03.47
Default text field size is 65535 instead of 32K.

3.10.03.48
Accepts dates and timestamps like this:

{d '2010-6-6'}

{ts '2010-6-6 3:3:3'}

3.10.03.49
For UPDATEs as well as INSERTs the error message for string literals that are too long is now very explicit and returns the first few hundred characters of the string that is too long.

3.10.03.50
Better error messages for service interruption situations.

3.10.03.51
Better error messages for situations where the licensing database does not exist.

3.10.03.52
ADO now will not stumble on null NUMERIC fields (fields in QuickBase with a fixed number of decimal places).

3.10.03.53
Better error messages especially for type mismatches.

3.10.03.54
QDBCommitTxn now reports errors correctly on CSVImport that were reported as No ErrorNoError.

3.10.03.55
Blocking of fetching rows is now done only for SQL Server. This had been causing a problem with PHP.

3.10.03.56
Added retrieval of Content-Type header to the UNIX code.

3.10.03.57
Better error messages for openSSL code in Unix.

3.10.03.60
getTableCatalogName now uses API_GetSchema instead of API_GrantedDBs.

3.10.03.61
Now handling Record ID# fields that have commas turned on.

3.10.03.62
Multi-line text fields are now always SQL_VARCHAR instead of SQL_LONGVARCHAR

3.10.03.64
Now username is output in trial expiration message. Also there is a connection string option to display uids instead of emails in user fields.

3.10.03.65
Now username and password is output on Invalid username and password error messages. Also better error messages when you have incorrect date, time or timestamp formats.

3.10.03.67
USEFIDS was being applied in all cases.

3.10.03.68
Bad password message now contains the MS Windows user and domain.

3.10.03.69
Parameters pulled from the ODBC,INI file can now be as long as 255 characters instead of just 63 characters. This matters for the FILEPATH parameter.

3.10.03.74
Error messages replace the file URL when writing file attachments to disk does not happen properly.

3.10.03.75
Error messages replace the file URL when creating directories for writing file attachments to disk does not happen properly.

3.10.03.76
Now the bad password error message tells you the QuNect product name. Also the [QuNect][QuickBase] prefix is replaced with [QuNect][HTTP] when HTTP errors occur.

3.10.03.77
The writing of a file attachment to disk error message now reports who the user is that is attempting the write operation.

3.10.03.78
Fixed bug caused by API_GenResultsTable only returning the first 1000 rows instead of all rows.
QuNect.exe
Created on Dec. 30, 2010 at 10:50 AM (EST). Owned by von Roesgen, Claude.
Claude von Roesgen
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:

Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.

We're glad you're interested in doing more with Quickbase!

Now we need to make you official before you share apps or manage your account.

Verifying your email lets you share Quickbase with others in your company.

Your work email
Your company