C
Craig S.
I have an ADP application that uses SQL Server. Its purpose is to load data
into a third party application that also uses SQL Server. My Application was
working fine until the third party application was upgraded.
Since the upgrade of the third party application I can no longer execute the
stored procedure from the ADP as it just stops inserting data into a table
and comes back to the ADP without finishing. If I run the stored procedure
from Query Analyzer it completes without any errors.
I have chased down that the upgrade third party application now takes much
longer on inserts because they have add a bunch more error checking in the
insert triggers. I know my stored procedure is working correctly because it
yeilds the correct answers when run from query analyzer. What I am looking
for is some ideas on how to find out why the my ADP quits in the middle of
runningt the stored procedure. It almost feels like it is timing out or
something. Any thoughts or ideas would be appreciated. Thanks
into a third party application that also uses SQL Server. My Application was
working fine until the third party application was upgraded.
Since the upgrade of the third party application I can no longer execute the
stored procedure from the ADP as it just stops inserting data into a table
and comes back to the ADP without finishing. If I run the stored procedure
from Query Analyzer it completes without any errors.
I have chased down that the upgrade third party application now takes much
longer on inserts because they have add a bunch more error checking in the
insert triggers. I know my stored procedure is working correctly because it
yeilds the correct answers when run from query analyzer. What I am looking
for is some ideas on how to find out why the my ADP quits in the middle of
runningt the stored procedure. It almost feels like it is timing out or
something. Any thoughts or ideas would be appreciated. Thanks