Hi Frank,
No please don't ignore us front-end-for-server-database users!
That said, with the driver structure in order (so the query language
doesn't change between servers), from the users perspective the database
back end is irrelevant, except for performance and multi-user issues.
We users (OK maybe just me) want to do things in 5 minutes, without
diving into the api documentation to write code (turning on a macro
recorder and edit bit is already to much for most). Then after a while
we take another 5 min. to improve the form, the query, the database
backend etc.
So instead of focussing on the performance of HSQL a wizard to move a
local databases tables, relations and queries to a server (postgresql in
my case) will solve every bodies performance issues if they are free to
choose the right backend.
For a user (once the database has been designed):
(getting the data in) - the ease of creating a form that does what he
wants is the most important issue. I believe a lot can be done in that
area (compare with MSA).
(getting the data out) - once I grasp what can be done with the
ReportDesigner ... in the meanwhile integration with Calc could be
improved. F.i. you can not set the parameters of your query from Calc
(not easily) so in most cases you need to manually select or copy
everything to the spreadsheet.
And what about displaying graphs from a form or report?
Notwithstanding the above, I won't be using MSA anymore (says a windows
user starting from v3.0 and Word from 1.1).
Ferry
Frank Schönheit - Sun Microsystems Germany wrote:
However, this is complicated by the fact that there are too many people
saying they use Base as front-end for server databases, and that it does
a reasonable or even good job there. We can't simply ignore this part,
which for a long time has been the only focus, of Base's identity.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
