ActiveX client programming, Java field programming tips

Using the ActiveX to Enterprise JavaBeans (EJB) bridge to access Java fields has the same case sensitivity issue that it has when invoking methods. Field names must use the same case as the Java field syntax.

Visual Basic code has the same problem with unsolicited case changing on fields as it does with methods. (For more information about this problem, see ActiveX to EJB bridge, calling Java methods). You might use the CallByName() function to set a field in the same way that you call a method in some cases. For fields, use VBLet for primitive types and VBSet for objects. For example:
o.MyField = 123                         'Incorrect...
CallByName(o, "MyField", vbLet, 123)    'Correct...
or in VBScript:
o.MyField = 123                          'Incorrect...
Eval("o.myField = 123")                  'Correct...



Related concepts
ActiveX to Enterprise JavaBeans (EJB) Bridge
Related tasks
Developing ActiveX client application code
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 4:16:02 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-dist&topic=rcli_xfield
File name: rcli_xfield.html