Author: Lennart Jorelid (http://www.jguru.com/guru/viewbio.jsp?EID=15) Question originally posed by John Zukowski PREMIUM (http://www.jguru.com/guru/viewbio.jsp?EID=7 Longer answer: You may create a digitally signed applet using a Certicate to circumvent the security sandbox of the browser. See the Certificate jFAQ.

Speed - We had an app that used the ODBC bridge to write data to an Access database. When we switched it over to use Jackcess, it was 5 times faster.

Most ODBC 2.0 drivers should work with the Bridge. Since there is some variation in functionality between ODBC drivers, the functionality of the bridge may be affected. The bridge works with popular PC databases, such as Microsoft Access and FoxPro.

No. The JDBC-ODBC Bridge does not support concurrent access from different threads. The JDBC-ODBC Bridge uses synchronized methods to serialize all of the calls that it makes to ODBC. Multi-threaded Java programs may use the Bridge, but they won't get the advantages of multi-threading. In addition, deadlocks can occur between locks held in the database and the semaphore used by the Bridge. We are thinking about removing the synchronized methods in the future.

Use of the JDBC-ODBC bridge from an untrusted applet running in a browser, such as Netscape Navigator, isn't allowed. The JDBC-ODBC bridge doesn't allow untrusted code to call it for security reasons. This is good because it means that an untrusted applet that is downloaded by the browser can't circumvent Java security by calling ODBC. Remember that ODBC is native code, so once ODBC is called the Java programming language can't guarantee that a security violation won't occur.

Yes. Most database vendors ship a JDBC driver with their database. We recommend starting with the JDBC driver written by the manufacturer of the database you are using. If the database you are using such as those from Microsoft did not supply a JDBC driver or you have needs that are not met by that driver, you can use a 3rd party driver. The following web page lists many JDBC drivers that are available:

No, this is just one of many possible solutions. We recommend using a pure Java JDBC technology-enabled driver, type 3 or 4, in order to get all of the benefits of the Java programming language and the JDBC API. You still need to get and install a JDBC technology-enabled driver that supports the database that you are using. There are many drivers available from a variety of sources. You can also try using the JDBC-ODBC Bridge if you have ODBC connectivity set up already.

Connection con = DriverManager.getConnection("jdbc:oracle:thin:@oracle.students.itee.uq.edu.au:1521:iteeo", "login", "password");

The JDBC adaptor was designed to allow use with any JDBC driver (hence any database that has a JDBC driver). However, the adaptor has to be certified with the JDBC driver as there can be some minor differences between drivers especially when it comes to the SQL they support and the metadata information they provide. We have certified the adaptor for Oracle, Sybase, JDataStore, MS SQLServer, Interbase and DB2 UDB.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) Oracle basically has two JDBC drivers: an OCI driver which includes native code and a Thin driver which is 100% Pure Java. Since the OCI driver includes native code, it cannot be used in applets. You must use thin driver. You can get all Oracle JDBC drivers from http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm.

The classes you need to import are all contained in the java.sql package. To import these classes, include the following line at the beginning of your code: import java.sql.* Untrusted applets cannot open connections to any machine other than the originating host. The originating host is the machine which provides the classes and may be the host from where the HTML page was accessed or the host specified in the codebase parameter in the applet tag. This is a Java restriction.

Our ODBC SDK enables our customers to develop a proof-of-concept, read-only ODBC Driver in less than a week, and a complete, fully-optimized read-write ODBC Driver with push-down functionality within three to six months.

This is very unlikely, but should this occur, you can use an ASCII text file to connect to LinkUP Enterprise. Please let us know if you are having difficulties in obtaining drivers, we may be able to work out a solution for you.

Method 1: Set the Java property sql.drivers using the Java -D option. The sql.drivers property is defined as a colon-separated list of driver class names. For example: intersolv.jdbc.sequelink.SequeLinkDriver: The sql.drivers property can be set like other Java properties, using the -D option. For example: java -Dsql.drivers=intersolv.jdbc.sequelink. Method 2: Set the Java property sql.drivers from within your Java application or applet.

Our bridge doesn't need a Pericom specific device driver. At the Windows 2000/XP level, the generic pci-pci bridge driver pci.sys is all that is needed, which comes with every windows. Linux (Red Hat 7) supported our bridge with no driver from us, using a default pci-pci bridge driver.

Yes! The Minisoft ODBC driver is ODBC 3.0 compliant. This means it also supports Remote Data Objects.

Problems with Visual FoxPro ODBC driver. Works well, but on closing the connections the application can trigger unexpected errors. This can happen on exit or on new package running. It is recommended to quit the application after all DBF-related processing was completed.

Rajkumar Seth offers the following: static void ftdsjdbc () { try { // use your hostname and port number here String url = "jdbc:freetds:sqlserver://nt1:1433/master"; String login = "sa"; // use your login here String password = "secret"; // use your password here if (false) { //Sybase url = "jdbc:freetds:sybase://unix1:4100/master"; login = "sa"; // use your login here password = "secret"; // use your password here } Class.forName("com.internetcds.jdbc.tds.

All databases supported by SequeLink 4.0, or higher, can be accessed through the SequeLink JDBC Driver. These include: The SequeLink JDBC Driver and SSL classes are packaged in the JAR files slje.jar and crysec.jar, which are located in the directory <installdir>/driver/classes. Copy these JAR files to your Web server and make sure that the JAR files are specified correctly in your HTML code using the codebase and archive tags in the applet tag.