Paul Clapham wrote:Sorry, no idea. I went to their website but since it's paid-for software they don't seem to have any documentation on-line. It's funny how you get used to the idea of applications putting their docs on-line.
Paul Clapham wrote:Oh, you mean that ERO.jar is on the web server? But your code uses a File object to load it. That means you're looking on the client machine for it.
Paul Clapham wrote:Okay. You're trying to read from the client's file system, so have you signed the applet? If you haven't then that won't work. However you should get a security exception which is visible in the Java console in the browser.
Also I see that you're trying to read from the current working directory. Have you actually determined what the current working directory would be for the browser you're using, and put the jar file into that directory?
Paul Clapham wrote:I still don't want to look at all that code. Especially since with applets, it's almost always the configuration rather than the code which leads to problems. Your next step should be to write a short simple compilable example which does nothing except the bit which is causing the problem. That would be something which you could reasonably ask somebody to look at.
It's probably some simple configuration thing, like you don't have the ERO.jar file in the right place. I don't think it should take more than 50 lines of code to display what you're trying to do there, maybe even as few as 20.