First, let me understand what's happening:
A client logs in via ODBC (takes 10 seconds or so to log in)
While client is logged in, a FM script runs that uses the CF FoundList to retrieve related record IDs
Those returned IDs are then populated into a global field then used for a GTRR
is this correct?
Yes, that’s correct – any ideas?
Can you relate that change in behaviour to a recently installed update?
Script runs on server? Is that ODBC client accessing the TO or table in question?
Just trying to get a catch of what may be the cause.
I doubt this is a record locking issue. You would get a 301 error in your script if so also, locking is only going to keep you from writing to a field on that locked record, not retrieving a list of related IDs.
It would not be a record locking, you can always read from a locked record and setting a global field does not lock the record...
Is the ODBC guest actively updating records? Could it be an index updating issue?
Thanks for your response.
The only thing I can tell thus far is ODBC client connects – breaks the script. ODBC client logs off, script works.
No script on server, not the same TO we’re using for the script on client desktop, same tables though.
That’s what I thought. The ODBC guest is only pulling records into a local table – no edit whatsoever.