This is a more specific version of my other question. I have created an applet that should communicate with my MS Access database. It works fine when I run it through a compiler, but when I embed the .class file in an html page and open the html page, it runs but none of the changes it is supposed to make to the database actually happen and it cannot retrieve data from the database. I am eventually going to publish this html file to a secure network. The applet should communicate directly with the database on the computer, without servlets/sockets/etc (even though this is supposedly not good practice). If a different computer accesses the html page, it should be able to run the applet and make changes to the database on the host computer, but it need not allow the applet any special access to its own files, since they are not being changed, only the database on the host computer is. So I see no reason to make it a signed applet, because that will enable the applet to make changes to any computer, not just its own. I run Vista so policy tool is not available.
Note: the html file, the class file, and the java source file are all on my computer in the same folder, and this is the way it will stay. The html file is not yet published, I just created it myself to test the applet.
I have actually attempted this sort of thing before. I think your problem lies in the nature of an applet.
Applets are downloaded and run by the client machine, so if the database that you are trying to access exists on the server, the client probably does not have access to the database location on the server. And as we all know, code from the client machine is not to be trusted.
It may be easier to rewrite your page as a servlet, as the servlet lives on the server and presumably has access to the database. Your servlet can then send html and receive form data back and forth between the client and server.
If your heart is set on an applet front end, you could send http messages back to a servlet which would then perform the database operations. This option would be far more secure and a lot easier to implement permission-wise.
Hope this helps, let me know if you have additional questions.