I would like to expand on something I allueded to in an earlier message.
The choice of HSQLDB for inorporation into OOoBase.
The issue of HSQLDB requiring Java for the creation of stored
procedures, is likely a straw man. Yes, it is on the surface a bit more
daunting to some then a native scripting languge, such as PL/SQL. But
the truth is that for the causual user PL/SQL is a huge hurdle in an dof
iself. So the isssue is possibly mute.
On another front however it seems like an excellent choice. There should
be a very natural upgrade path for a company if they choose OOBase. In
the embedded form it would allow quick development of a stand alone,
single user application. The file based and server models of the engine
should, on the face of it, offer a natural path to move to larger number
of concurrent users without signigicant changes to the application.
Another way to view this would be if a small company used the server
model first, to support in house users. While creating a single user
version of the application for use on outside staff laptops.
I hope that these type of implementations are in the vision of what
OOoBase is to become.
Andrew Jensen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
