Hi Carey,
Thanks for the reply.
Yes, you are correct, by Version 4 API I mean ARSPerl
built against the version 4 API libs.
Here is what I am trying to accomplish... basically, I
have written a filter to initialize a global field using
a Set Fields action. The value is read from a parameter
Larry,
Thanks for the details on what your doing. It does help me to
understand what could be going on and to provide a few ideas on how to
troubleshoot this. As far as I know the idea of a global (or window
local) field is all in the client layer. I do not believe the server
does anything
Hi Carey,
Thanks for the troubleshooting suggestions. I'll let you
know what I discover. I appreciate your time.
Larry
On Mar 19, 2008, at 9:22 AM, Carey Matthew Black wrote:
Larry,
Thanks for the details on what your doing. It does help me to
understand what could be going on and to
Hi Folks,
I think I have an API version incompatibility. Can someone
confirm that ARS version 5 was when Global fields were
first introduced? I have check the various documentation
sets and the version 5 set is the first mention of Global
fields that I could find. In version 4, the
Larry,
I doubt that the Global field idea is where the hang up is. I would
guess that it is more likely a 'Date' only or 'Time' only, or some
other data type before it is a field ID range that is an issue.
But in fairness... some pretty bizarre behavior is hard to
understand too. Can you be any
5 matches
Mail list logo