Re: TEMPLATE, LIKEFILE and HANDLER

I'm also interested in this... I wonder what the rationale for making this not work with OA was? Is it harder to make this work with OA than a standard file? Or is there something about the nature of OA (I can't think of anything) that would make it less effective with LIKEFILE?


On 6/26/2015 1:28 PM, RJM wrote:

I started locally defining files and passing them to other procedures as
parameters when I do new development. Of course I defined the file globally
as a TEMPLATE and then use LIKEFILE to define it locally where it is used.
Today I tried to apply the same concept to a WORKSTN file, but using an Open
Access handler provided by a 3rd party vendor. Well, the HANDLER keyword
does not play well with the TEMPLATE and LIKEFILE keywords. You can't
define the HANDLER at the global level with the TEMPLATE keyword, and you
can't define it locally with the LIKEFILE keyword. So, I could define the
WORKSTN locally to the procedure with the HANDLER and not be able to pass it
to other procedures, or define it globally if it is needed in multiple
procedures.



Does anyone know if IBM plans to make all these keywords work together?