J
Jeff Ledbetter
Guest
Since I wrote the called code, I will comment. 
The code is not "legacy code"; it is the server API layer for our plug-in client. The procedure is this particular layer is returning a TABLE-HANDLE (not an HANDLE) and cannot return an encapsulated ABL object because it is coming across the appserver whose principal receiver is a java client. The TABLE-HANDLE parameter translates into a resultSet when invoked via java via the proxy-generated classes. So as one can see, it's not always black and white. Sometimes you gotta build for the gray areas as well. Anyhow, yes Thomas you should always do a DELETE OBJECT for TABLE-HANDLE parameters.
Continue reading...
The code is not "legacy code"; it is the server API layer for our plug-in client. The procedure is this particular layer is returning a TABLE-HANDLE (not an HANDLE) and cannot return an encapsulated ABL object because it is coming across the appserver whose principal receiver is a java client. The TABLE-HANDLE parameter translates into a resultSet when invoked via java via the proxy-generated classes. So as one can see, it's not always black and white. Sometimes you gotta build for the gray areas as well. Anyhow, yes Thomas you should always do a DELETE OBJECT for TABLE-HANDLE parameters.Continue reading...