SQL 2000 Stored Procedure Problem
I made some mods to the failing SProc and zeroed in on INSERT statement. I used a few Blocks of code (from your tutorial) in the SProc to force errors to see what happened. The “Force Error” block works as expected when it is before the “INSERT” - but when it’s after the INSERT the app does not get the error message and the recordset fails to OPEN. If I move the “– BLOCK: Trap Error” Just After the INSERT - No error message is returned to the app.
…
Server1 (older) does use linked servers since that’s where the web site resides and it has to read from either Server - it works fine. Ultimately Server1 is going away - and the linked server will no longer be needed. But this problem app does not use it - it is just a Reports App and the server that has the app will always be the same server that has their SQL Server and Database. The full “IP.DBName.[dbo]” is simply used to make it easier to manage since the IP and DB are in a Setup Table that depending on the customer the IP “may” be different and the DBName will always be different.
…
Website: www.derkeiler.com | Filesize: 9kb
No of Page(s): 4
Click here to download SQL 2000 Stored Procedure Problem.
Related Tutorial
Tags: database server, SQL, SQL Server, stored procedure
Comments
Leave a Reply