3.11.04.37
3.11.04.37 
Fixed bug with UPDATE queries in MS Access. Moved the clist set from the LPSTMT level to the lpQDBTableDef level. Also bypassing the Node Comparison if all criteria and sorts were pushed down.

3.11.04.36 
Fixed bug that caused the catalog filter to fail. This caused problems in Excel and Visio.

3.11.04.34 
Now works with Crystal Reports 11.

3.11.04.33 
DSN config dialog now allows setting of which characters appear in field names.

3.11.04.32 
DROP TABLE will work with a parent dbid but it will try to find the child table with a matching alias. If it can't it will report an error. In no case will it delete an application.

3.11.04.31 
MS Access export of all numeric field types except Replication ID now works.

3.11.04.30
DROP Table now works but not for applications, only for tables. This is to prevent MS Access from deleting the application it's trying to create a table within.

3.11.04.29 
DROP Table now works but not for MS Access. This is to prevent MS Access from deleting the application it's trying to create a table within.

3.11.04.28 
Export from MS Access to QuickBase now works with Long Integer fields.

3.11.04.27
Export from MS Access to QuickBase now works.

3.11.04.26
Cleaned up the calls to predicatePushedDown. Reworked the traversal of the sort tree.

3.11.04.25
Reworked the traversal of the criteria tree.

3.11.04.24
Checking for pushdown criteria and sorts before assuming that we can fetch only the rids via a rid list.

3.11.04.23
Now SELECT statements that have only the built-in field Record ID# as the result column will only need to fetch the ridlist via API_GenResultsTable, which will really speed things up.

3.11.04.22
Now single row QDBPrepare statements like SELECT @@IDENTITY use a RID of zero and a FID of zero.

3.11.04.21
Just getting the rid uses only the rid list.
Now if the only thing you need is the RID it uses the RidList instead of fetching the record.

3.11.04.20
The list of fields for each table is now stored at the statement level instead of at the connection level.

3.11.04.19
QDBPrepare now does the parsing and uses the parser exclusively to determine if there is a possible optimization for the COUNT aggregate.

3.11.04.18
SELECT count(1) FROM a single table with no where clause is optimized.

3.11.04.17
Underscores in table search pattern are properly unescaped.

3.11.04.16
Fixed the scalar REPLACE function.

3.11.04.15
Criteria are pushed down to QuickBase even when doing joins now.

3.11.04.14
Better error for columns missing from GROUP BY column list.

3.11.04.13
Can delete current revision of file attachments and error message for trial expiration displays the QuickBase username of the user whose trial is expiring.

3.11.04.11
IN clause did not work with text fields.

3.11.04.10
You can put hyphens back in field names with connection string parameter FIELDNAMEHYPHENS.

3.11.04.08
Criteria are pushed down to QuickBase again after they were not pushed down starting in rev 152, except in the case of a JOIN. So userfields whose value is a screenname will not match to an email address supplied via the where clause when doing a JOIN. But on simple SELECTs it should work fine.

3.11.04.07
FLOOR on a negative number no longer causes an end of buffer overwrite error.

3.11.04.06
Scalar function replace now throws an error if you try to operate on fields with more than 65535 characters of data.

3.11.04.04
Scalar function replace now throws an error if you try to operate on fields with more than 255 characters of data.

3.11.04.03
Hyphens are no longer part of field names or table names.
ifdef a line of code that was windows specific so that it would compile in Linux.
This is for Unix builds only.
Added icons in the Start menu for ODBC Admin panel

3.11.04.02
Date Modified field is not Nullable just like Record ID#

3.11.03.99
Illegal XML characters are converted to spaces.

3.11.03.97
No you can do round trips with file attachments.

3.11.03.96
SELECT TOP now works with four part names in SQL Server

3.11.03.95
Can name a proxy server explicitly now.

3.11.03.94
QuickBaseClient::rewind
lpQDBTableDef->iRecordsToSkip is not incremented by one before comparison

3.11.03.93
Simplified QuickBaseClient::rewind. No special case for record id.

3.11.03.92
Fixed a potential bug in QuickBaseClient::rewind.

3.11.03.91
Fixed a bad bug in QuickBaseClient::rewind. This caused things to crash.

3.11.03.90
Fixed a bad underflow bug in QuickBaseClient::rewind. This caused things to hang.

3.11.03.89
Now if the rewind counter is greater than 1 we don't dump the table cache.

3.11.03.88
The compares are done now even when a criteria has been pushed down to QuickBase.

3.11.03.87
Join optimization code was not coordinated with push down of criteria to QuickBase.

3.11.03.86
Fixed crash due to iterator increment beyond end of vector in record fetching.

3.11.03.85
Will not get tripped up on quotes inside square brackets or vice versa. Also Long table names will not screw up MS Access.

3.11.03.84
Now sorting keeps the table cache from being cleared which had been causing a bug.

3.11.03.83
SUBSTRING function negative argument for length counts back from the end of the string for the stopping point.

3.11.03.82
SUBSTRING function now accepts a negative argument for length and will produce an empty string if the arguments are out of bounds.

3.11.03.81
Fixed a memory leak in the UNIX versions due to not doing an SSL_free.

3.11.03.79
This is the first release of the Mac 2011 version!
Can download all revisions of file attachments.
Created on Nov. 18, 2011 at  9:20 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