Posted Wednesday, December 31, 1969 @ 23:59:59  

Hi Benjamin,

I am excited about your product, since it covers a lot of ground that I
had intended to code myself. Before I start:

(1) Do you use threads to make inquiries faster, and to maintain the
user's sense of control over processes?

Currently we don't use a separate thread to query & load the data. The user
can always call the refresh() method in a separate thread which would get the
results in a different thread.

(2) Do you focus your sql queries so that you only get one screen at a
time (from a sql view ), or do you try to load the entire result set
into the data vector for your jtable? My program may retrieve hundreds
of thousands of records, so it would be impossible to wait around long
enough for whole result sets to load.

Only visible records will be fetched from database. This is the feature
which most users like in Quicktable.

(3) Do you have individually resizable rows, so that if content for a
given row is taller than another row, the content can still be shown
completely? Or can I override the table settings to facilitate this
myself?

QuickTable allows to set the row height of all rows, it cannot set the
height of different rows differently. But you can always get the jtable
from quicktable & change the heights of different rows as needed.

(4) Can I generally override most of the features of the jtable,
including the various cell renderers and editors?

generally you can override the features of jtable. But just know your limits, for
example, if you add a new column to jtable,there might not be any data available for that
column.For celleditors & renderers, your editor/renderes classes should implement the interface quick.dbtable.CellComponent

(5) If I buy the code, do I get updates and bug fixes as well?

Yes, you will get all the updates & fixes.

Thank you for creating this marvelous product,