Hello Ray, > * wait for OO API to support Connection and XConnection conversion > > Waiting period is uncertain. > Waiting time is not likely on my side.
I meawhile even think this might be impossible. If you connect to a running OOo instance, which may run in another process, then you have two JVMs involved. Transporting the java.sql.Connection object from the one JVM to the other might be completely impossible, architecture-wise. > * temporarily directly access the database content in *.odb > by circumventing sdbc.XConnection > ... > * eliminate OO Base *.odb from the integration list > ... > * switch to MS platform (MS Access, C#, etc.) No good ideas :) > * any other paths? Marc's idea with a HSQLDB server, which can be connected from both Base and other applications, sounds like a good idea to me. You loose the all-in-one-file then, of course, not sure how much this is a limitation in your scenario. Also, it still means you have two separate connections to the DB, while in your original sketch, you would have had one connection only. Again, not sure how much this is a limitation for you. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
