So I guess when you say "the code here works fine", what you really mean is: "the code here doesn't work fine"
It's hard to say what code you don't show us might or might not be doing. But the combination of applets and databases suggest two possible problems, both related to the restricted privileges of applets: - the DB host is not accessible to the applet (because applets can only connect to the host where they were served from) - the driver classes are not part of the applet (or use native libraries), and so the driver can't instantiate them
You can information on how to work around these issues here.
If it's neither of these, you can post the relevant code with an indication of where it fails to execute properly.
- Generate webpage only - Run applet in appletviewer [thats what i choose] - Run applet in web browser
!
in the appletviewer, there is an Applet menu>>>>Properties>>>> - http Proxy server (with an empty field) - http proxy port ('80') - Class access (option- 'Restricted'/'Unrestricted') (Command buttons 'Apply', 'Reset' & 'Cancel'
it was on restricted, but now i changed it, and i dont know if it will make any difference, because i'm still debugging my code, so i havnt checked! [ January 04, 2006: Message edited by: H Melua ]
In that case, if you run the applet locally in your browser, make a note of the URL you see there. It should be something like "file:///path/to/directory/index.html". Then you can use "file:///path/to/directory/-" instead of "http://YOUR.SERVER.HERE/PATH.TO.YOUR.APPLET.HERE/-". Just remember to add the proper policy for the server later.
Jeanne Boyarsky
,
author & internet detective
staff