×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 09/14/2017
02:03:13 AM:
connect is not allowed in a trigger or function and so connect reset
won't
work in your SQL error routine and it should not be necessary, there is
only
the local connection.
Did you try to invoke the function lacally and what did happen then?
I guess I shouldn't have used the word "function". There is no
SQL function (or trigger) involved. I was referring to a network
application function, request, or selection. As for the stored procedure,
I can execute it one or more times locally and it works fine every time. I
can execute it one or more times from iNavigator and it works fine every
time. It can be executed one time from MS SQL Server on the network and
it works fine. The only problem is when it is executed a second time from
MS SQL Server on the network over the same ODBC connection. The same
network user can wait 1 minute between executions from MS SQL Server and
it works fine every time. But when the network user makes the request
from MS SQL Server twice within 30 seconds the second request always
fails.
Sincerely,
Dave Clark
As an Amazon Associate we earn from qualifying purchases.