Joe
I don't know that I can quite go along with your assertion, that it is
necessary to know whether your native IO is being "handled". It kind of
goes against the whole idea of Open Access: RPG - to have a transparent
means to work with non-tradtitional data sources and hardware. The
handlers are called by the normal RPG runtime, and one major point is,
you don't have to change anything, other than a keyword, in order for
your code to work with something like a browser or an Excel workbook.
I do agree, Tom should go to ASNA to resolve this. I know that an issue
of not having a device associated with a lookSoftware browser rendering
of an app on i was resolved quickly by them when a mutual customer
needed the change. These are all companies that will work with
customers, so far as I can tell.
This list is maybe the last place to ask vendor-specific questions,
especially at the beginning of the use of this new technology. Not
enough of us are using these things yet, for there to be a community
base of knowledge.
Vern
On 9/17/2011 9:09 AM, Joe Pluta wrote:
Sorry to hear that, Tom. Every company that provides an OA handler
should provide an API to identify whether or not you're running under
OA. It's just common sense (and common courtesy). An API like the one
I outlined in the earlier post is very easy to implement. Maybe you
could ask ASNA nicely to implement it? :)
Joe
I do not have control over the OA hander.
It appears there is no easy way to do this from the posts and research done.
Tom Deskevich
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.