Did you mean =:or:=in the following line:
("ItemID=:1";$tItemID)
Roger T. Reed
> On Jul 27, 2018, at 3:41 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Jeff,
> You know - something wrong. ;-/
>
> Maybe a control char? Chars outside of regular ascii? If it's
Jeff,
You know - something wrong. ;-/
Maybe a control char? Chars outside of regular ascii? If it's possible this
value could have been pasted in from some external text it might have some
wonky char in it that looked pretty but chokes here. It's happened to me.
May be impossible there. Agreed
> On Jul 27, 2018, at 1:52 PM, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> It's also annoying that an error handler is running, yet a runtime error
> appears instead of calling the error method. Also the lack of a call chain
> makes this really hard to track down.
So.
What would you check for? $1 is a text so it will either have a value or be an
empty string -- both of which can be queried for. And testing the length of
the entity selection prior to trying to access the first() element prevents
another runtime error if the query returned nothing.
It's also
Randy,
I'd add a check to the item ID string. ORDA is excruciatingly picky in
terms of inputs. I bet something is not completely kosher in an item id and
that's causing the RT error.
Alternatively you could loop through the list of items and check the id
there. But if the param is generated or
It looks like ORDA may be 99.9% reliable, just like 4D SQL.
I just had my first random, no explanation runtime error from a method I
converted from SQL to ORDA. The code has been live for a day and a half - looks
like it failed sometime early in day 2.
The code:
C_TEXT($0;$tManufacturer)
6 matches
Mail list logo
