Dear Ashok: Thanks for the suggestion.
> why dont you use the java.sql.connection class library directly? > you can use the full java.sql.* library api set from within > Java UNO client application. The case for OO *.odb database files is not as simple as suggested. Each OO *.odb file (actually in ZIP format) currently contains other elements in addition to the database contents. It is possible [1] to circumvent com.sun.star.sdb.* and directly access the internal database elements in *.odb files using only java.sql.*. However, this approach is not considered a robust design as OO Base is free to revise the internal structure for future feature support. It will not fly in a medium size business environment in the presence of competing bidders (MS, etc.) for project funding. In general, keep the freedom where it belongs. OO Base and API teams need freedom to improve the OO market competitiveness. OO application teams need freedom to compete for product funding. These two types of freedoms rest upon competitive API architecture designs. (competitors: MS, and others.) Recall that OO UNO is implemented in C++ and that my example application is in Java. The OO API and Base teams are very capable talents. They perhaps can figure out competitive designs [2] similar to the virtual functions in C++ (polymorphism). It might be one practical way to solve this business problem. Thanks again for feedback. Ray [1] digiassn.blogspot.com/2006/07/java-creating-jdbc-connection-to.html [2] publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm. xlcpp8a.doc/language/ref/cplr139.htm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
