Dear Marc: Thanks for your time in the deliberation.
> Use HSQL in server mode (as opposite to OO.o-embedded mode) and let OO.o and the custom java applications connect to them as needed. Yes, this approach would work, as found in my previous trial. OO is almost completely out of the picture, though. It changed the integration list to: application (Java) + GUI (local spreadsheet) + data 1 (local, any RDBMS, nothing to do with OO) + data 2 (JDBC RDBMS) + data 3 (JDBC RDBMS) + etc. If future conversion to OO *.odb (embedded HSQLDB) is desired, I need to figure out a robust approach to package (ZIP) various elements into the *.odb format. Developers Guide 2.0 does not provide guideline on manual *.odb packaging. Trials with java.util.zip provided empirical answers, but no guarantee when OO Base evolves. > the distribution boils down to a software distribution (HSQL and the data files) and configuration management problem. Deployment, version update, configuration management, etc., all touch upon the sensitive issue of user PC access and privilege control in medium size business environment. It is related to my previous private discussion with Juergen Schmidt on "API document script access". Juergen has encouraged me to repost some of the private discussion on [EMAIL PROTECTED] (not [EMAIL PROTECTED] ?). I shall try ASAP after obtaining his consent (which sections?) and when I am between tasks. Thanks for the discussion. Ray --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
