Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL Server Problem
Message
De
03/12/2007 08:43:47
 
 
À
03/12/2007 06:05:49
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Versions des environnements
Visual FoxPro:
VFP 8
OS:
Windows Server 2003
Network:
Windows 2003 Server
Database:
MS SQL Server
Divers
Thread ID:
01272682
Message ID:
01272769
Vues:
13
Never name your stored procedures with sp_ prefix. MS use that prefix for internal use.
That is not the problem here.


>Christof:
>
>See my original post below:
>
>I get the error below from the SQL Server Query Analyzer. I tried that after having problems with VFP.
>
>VFP SQLEXEC() returns a nesting level exceeded error after freezing for a while.
>
>I put the script that creates the procedure at the end of this message.
>
>Thanks
>
>Bill
>
>
><<
>When I run a stored procedure that takes parameters and updates a table on my machine here, it works fine.
>
>Running the same procedure at the client, I get
>connectioncheckfordata
>General Network Error
>Connection Broken
>
>When I run a script that just updates the same table for the same fields at the client, it runs OK, but when I run the SP with passed parameters, it crashes.
>
>I googled it and saw one answer that said "network problems" but nothing specific.
>
>Any clues?
>
><<
>
>
>Hi Bill,
>
>it runs OK, but when I run the SP with passed parameters, it crashes.
>
>What do you mean with "crashes"? Does VFP suddenly disappear, do you get a C5 error, does SQLEXEC() return -1, do you get an error message, is SQL stopping?
>
>Do you get any sort of error message or error code? When execution fails, you can use AERROR() to retrieve error details. Please note that with ODBC errors AERROR can return more than one error at once.
>
>What happens when you run the same stored procedures with parameters in Query Analyzer or SQL Management Studio?
>--
>Christof
>
>
>IF OBJECT_ID('dbo.sp_updatemsmast') IS NOT NULL
> DROP PROCEDURE dbo.sp_updatemsmast
> GO
>CREATE PROCEDURE sp_updatemsmast
>@id_col INT,
>@userid CHAR(4),
>@deanum CHAR(10),
>@hinum CHAR(15),
>@memnum CHAR(15),
>@company CHAR(35),
>@contact CHAR(20),
>@title CHAR(20),
>@address1 CHAR(30),
>@address2 CHAR(30),
>@city CHAR(20),
>@addrstate CHAR(10),
>@zip CHAR(10),
>@phone CHAR(20),
>@email text,
>@country CHAR(15),
>@faxno CHAR(20),
>@saleclass CHAR(5),
>@memsince datetime,
>@parentid INT,
>@termdate datetime,
>@division CHAR(30),
>@msstatus CHAR(1),
>@source CHAR(1)
>AS
>UPDATE msmast
>SET deanum = @deanum,
>hinum = @hinum,
>memnum = @memnum,
>company = @company,
>contact = @contact,
>title = @title,
>address1 = @address1,
>address2 = @address2,
>city = @city,
>addrstate = @addrstate,
>zip = @zip,
>phone = @phone,
>email = @email,
>country = @country,
>faxno = @faxno,
>saleclass = @saleclass,
>memsince = @memsince,
>division = @division,
>termdate = @termdate,
>parentid = @parentid,
>msstatus = @msstatus,
>source = @source,
>lckstat = '',
>lckdate = GETDATE(),
>lckuser = @userid
>WHERE id_col = @id_col
>GO
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform