Applet problem with IE5

I have a client who upgrade his browser to IE 5 and the latest java vm but he still receives this error: com/island/chicago/inlet/Inlet.jbInit: type
mismatch: actual type jclass/bwt/JCTabButton, expected type
      at com/island/chicago/inlet/Inlet.init
      at com/ms/applet/AppletPanel.securedCall0
      at com/ms/applet/AppletPanel.securedCall
      at com/ms/applet/AppletPanel.processSentEvent
      at com/ms/applet/AppletPanel.processSentEvent
      at com/ms/applet/
      at java/lang/

Several other people running the same version browser and java vm do not have a problem.  He's running windows NT.  

Is there something I should look at in NT as the cause of this problem?  Has anyone encountered this problem before?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I suppose that all the other people have installed JBuilder ...
richpAuthor Commented:
This was on the client side using only a browser.  

I thought if a client has the same browser version and virtual machine the applet should run and it does for the majority of the clients.
both IE and NN on Windows will load classes from the system classpath automaticly. so if your applet uses some borland classes some browsers may load them from the local classpath.

just a guess :)
Angular Fundamentals

Learn the fundamentals of Angular 2, a JavaScript framework for developing dynamic single page applications.

richpAuthor Commented:
Wouldn't those classes be loaded from the jar file?  If not, are you saying that user may have a local copy of a non-compatible borland class?
'If not, are you saying that user may have a local copy of a non-compatible borland class?'

yes - this is possible.
I can't work directly with your enviroment, so I'm just guessing ...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
richpAuthor Commented:
It was a borland class but a klgroup class. The user had another jar file in his classpath which contained non-compatible jclass class files.  
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.