Integration

The matter of the driver being on the run-time class-path of the applet, and its ability to connect to 'home' or remote servers is quite different.

The driver will need to be on the class-path for either. To achieve that, add the mssqlserver.jar to the archive attribute of the applet element.

To connect to a DB on a remote server, the applet would also need to be digitally signed (by you) and accepted (by the end user).

Thanks for you reply,
can you please tell me how to digitally sign the applet

Hope this help:

<object
classid = "clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
width = 1 height = 1
name = "Application Web Client"
codebase = "http://java.sun.com/j2se/1.4.1/download.html">

<param name = CODEBASE VALUE = "." >
<param name = ARCHIVE VALUE = "myjar1.jar,
sqljdbc4.jar"
<param name = CODE VALUE = "applet.myapplet.class" >
<param name = NAME VALUE = "Application Web Client" >
<param name = "type" VALUE = "application/x-java-applet;version=1.1" >
<param name = CLIENT_INI VALUE = "client.ini">
</object>

Nicely done!

If they gave prizes for worthless advice here, you'd definitely get one.

See the Generating and Verifying Signatures lesson (http://download.oracle.com/javase/tutorial/security/apisign/index.html) of the Java Tutorial.

See also http://stackoverflow.com/questions/4897758/connecting-to-remote-databasemssqlserver-using-applet

I suggest you have your applet talk to a servlet. The servlet actually talks to the database (and holds the userID/password). This way, you aren't embedding the userID/password to the database in the applet where someone might get it and have direct access ot your database (a security concern).

I also suggest you review your design to see if separation of concerns might be a better choice (model view controller (MVC) design).