|
If you Google on "applet" and "sandbox" you'll find many articles explaining how it works and how to work around it.
We use applet signing for one of our applets we deploy. You get a confirmation window that confirms you want to allow the applet to download and run with access. From then on, you don't need to bother with the confirmation. A signed applet then has more access to local client resources.
Perhaps that might be a solution IF your problem is due to the "sandbox".
Pete Paul Raulerson wrote:
LOL! I think you know much more than I - there is a sneaking suspicion in the back of my mind I am trying to do something silly, since there doesn't seem to be examples of it around. :) The applet class comes up and initializes fine - the only error I can detect is that after I do a SETATR on the ODBC part on it's creation event, I come back and check the CONNECTED attribute, and find it is not connected. When run from Windows, it connects just fine and works as expected. This is probably something pretty basic to the idea of using Java Applets that I am misunderstanding. Perhaps the idea of having an applet that remotely connects to the database is a bad idea in the first place? It seems like such an easy answer to a simple low volume problem...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
