G
Guest
I have an adp project connected to a SQL Server 2005 database.
I have been trying to execute a very simple stored procedure that simply
clears two tables:
DELETE FROM tbl1
DELETE FROM tbl2
Executing this procedure from anywhere (Access 2007, SQL Server 2005)
generates a message: "The stored procedure executed successfully but did not
return records." When I run this using the DoCmd.OpenStoredProcedure in a VB
module, the stored procedure generates and error and returns the above
message. I have tried using SET NOCOUNT ON in the stored procedure and
"DoCmd.SetWarnings False" in the VB code, but they don't seem to have any
affect. How can I get around this???
VB Code snippet:
On Error GoTo ErrorExit
DoCmd.SetWarnings False
DoCmd.OpenStoredProcedure "dbo.myStoredProedure"
....
....
ErrorExit:
I have been trying to execute a very simple stored procedure that simply
clears two tables:
DELETE FROM tbl1
DELETE FROM tbl2
Executing this procedure from anywhere (Access 2007, SQL Server 2005)
generates a message: "The stored procedure executed successfully but did not
return records." When I run this using the DoCmd.OpenStoredProcedure in a VB
module, the stored procedure generates and error and returns the above
message. I have tried using SET NOCOUNT ON in the stored procedure and
"DoCmd.SetWarnings False" in the VB code, but they don't seem to have any
affect. How can I get around this???
VB Code snippet:
On Error GoTo ErrorExit
DoCmd.SetWarnings False
DoCmd.OpenStoredProcedure "dbo.myStoredProedure"
....
....
ErrorExit: