🚀 go-pugleaf

Here is one thing that REALLY seems to be a crucial design question. I
question how much Borland bound the DataSet property throughout the Model,
ColumnModel, and View architecture of JdbTable. I wish there were more
separation especially between the dbTableColumnModel and the dbTableModel
classes and the dataset property. The dataset property is required in both
the dbTableColumnModel and the dbTableModel classes. This may be because the
column model is not looked on as a "view" of the table model. However, one
would assume that JTable was meant to have a total separation between the
TableColumnModel and the underlying data. I think somewhere in here, it is
possible that Borland has tied all these classes together hence making the
ability to custom control the columnModel in JdbTable difficult.

Thanks for any and all answers.. Sincerely,  tommycox@mindspring.com

Warning: -- paragraph below is non-technical and expressed in frustration --
if you don't want to hear it please IGNORE -

If I am wrong please feel free to correct me. In that event, I admit massive
confusion. However there is little or no documentation available ANYWHERE on
INPRISES PATHETIC developer support web site. Of course, we all know that,
and I hate to complain about the obvious.  I guess that if I am having these
questions as an advanced programmer new to Java.. that I assume others would
also.. and would assume that more extensive FAQ's would be available. But,
in the tradition of Borland.. we developers hack on. Apologies for
complaining offered in advance.