Solution:
1. Check if a recordset or connection is opened before recordset operation is performed.
2. If stored procedure is used while retrieving the data to recordset, REMEMBER to use "SET NOCOUNT ON" at the beginning of the stored procedure. This is a problem which usually occurs when multiple actions are executed in a stored procedure.
3. Again, if stored procedure is used, make sure the stored procedure does return a record. Otherwise, make sure there is a routine in the code checking if the record doesn't return nothing.
e.g.
create procedure dbo.spr_getData
as
set nocount on
select ......
select ......
set nocount off
0 comments:
Post a Comment