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.

Yes, the SequeLink JDBC Driver is 100% Pure Java. No additional components need to be installed on your client workstation, other than an implementation of the Java Virtual Machine. For more information about SequeLink Java Edition Client product requirements, refer to the SequeLink Java Edition Client Installation Guide.

You can access almost every database from any university computer - library, computer labs, dorm rooms, offices, etc. - so long as it is hooked into the university's computer network.

About seventy percent of the databases that we subscribe to can be accessed from off campus computers.

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.

If you are a student, faculty, or staff of LSU, you can access databases and ejournals from anywhere that has an internet connection. Simply use the Libraries' webpage as you normally would, and enter your user ID and PIN when prompted. If you don't know what to enter see the User ID and PIN section of this FAQ. If you are not affiliated with LSU then you may not access our resources off-campus.

No. CD-ROM reference databases are accessible only on certain computers near the Reference Desk in the library. Ask a reference librarian at the Reference Desk for assistance. Other CD-ROMs can be checked out of the library; these can be found through the online library catalog.

Once your student photo I.D. is activated, you will be able to access the library's catalog remotely from home, work, etc. Remote access to other electronic databases is explained on a handout available at the circulation counter. You will be welcome to use materials within the library. Permission to check out an item will generally be refused; however, your request may be granted at the discretion of the librarian.

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.

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.

No. DataDirect XQuery™ 3.0 provides an XQuery engine as well as XQJ API implementation. DataDirect XQuery™ 3.0 embeds the DataDirect JDBC drivers as part of the product for relational access.

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

JDataStore is a Pure Java ORDBMS and includes JDBC Type 4 Local and Remote Drivers. A development license for JDataStore is provided on the VisiBroker CD. The installation is fairly easy. You can look at the online guides that come with it. Please note that when you create a JDataStore database, you need to set/associate a transaction manager (TxManager) with it.