Yep, the problem mutated from a not working query into the discovery how
misleading or plain wrong the client side log is.
> On 16. Mar 2018, at 16:32, LJ LongWing wrote:
>
> ok...so there isn't actually a problem?
>
>> On Fri, Mar 16, 2018 at 9:26 AM, Thomas Miskiewicz
>> wrote:
>> LJ,
>>
ok...so there isn't actually a problem?
On Fri, Mar 16, 2018 at 9:26 AM, Thomas Miskiewicz
wrote:
> LJ,
>
> the server side log shows that Mid Tier Client Log is plain wrong!
>
> The server side log shows that the filter I mentioned in my original post
> DID find what’s expected but a filter a s
LJ,
the server side log shows that Mid Tier Client Log is plain wrong!
The server side log shows that the filter I mentioned in my original post DID
find what’s expected but a filter a some time later fails instead.
Thanks
Thomas
> On Mar 16, 2018, at 3:19 PM, LJ LongWing wrote:
>
> Thom
Thomas,
What does the server side sql log show when you try to run the setfield
through a filter?
On Thu, Mar 15, 2018 at 10:09 AM, Thomas Miskiewicz
wrote:
> Hi Listers,
>
> I got a strange problem: a filter is doing a set fields and finding
> nothing. I can find the record using the GUI though
Hi Listers,
I got a strange problem: a filter is doing a set fields and finding nothing. I
can find the record using the GUI though.
In the client side log I see:
SELECT * FROM (SELECT AR_SQL_Alias2171 FROM (SELECT
T4474.C536870919, T4474.C1 FROM T4474 WHERE ((T4474.C536870921 =
'
5 matches
Mail list logo