The following is from KM198479, if you have an HP login you can access this document from here: [http://support.openview.hp.com/selfsolve/document/KM198479]. I hope this helps:
**The user's application contains some controls that look and behave like familiar controls, such as trees, tables, or buttons. However, QuickTest Professional (QTP) recognizes these objects as JavaObjects, not as their expected object types.
Example: The application contains some controls that look and behave like a JTree or JTable control. QuickTest Professional (QTP) recognizes these objects as JavaObjects, not as JavaTree and JavaTable objects as expected.**
**Diagnosis: The problem controls are customized controls that are derived from a standard class, such as a Panel (java.awt.Panel), that QuickTest Professional identifies as a JavaObject. For QuickTest Professional to recognize a customized control as the type of control it is, it needs to be derived from that class or an equivalent class. For example, to recognize a customized table as a JavaTable, it must be derived from a JTable (java.awt.JTable) or an equivalent Java class.**
**Write custom functions that use the control's properties and methods QuickTest Professional's Java add-in will allow you to access the Java control's own methods and properties. You can use these properties and methods to build your own functions for QuickTest Professional to use.**
**You can use the Object Spy or the ''.object.MethodWizard'' method to see which methods are available for the control.**
**Note: The properties and methods that are available with the .Object property come directly from the control in your application. Because of this, Mercury does not have any information (documentation) on what they do. If you need additional information on these properties and methods, you should consult with your developers.**
**Once you know what methods are needed to perform the desired action, create a custom function that QuickTest Professional can replay.**