Hello Peter,

p> I am using the .NET extension for firebird, and I am calling a stored
p> procedure (that uses a SELECT statment). There is always at minimum 1
p> record returned when calling the stored procedure (through .NET
p> interface), even when there should be no records. Is this a standard
p> behavior?

Do you have a selectable stored procedure (which SUSPENDs when it
needs) in a SELECT statement? Or do you use an executable stored
procedure (no SUSPENDs) in a SELECT statement or in / instead of
EXECUTE PROCEDURE statement?
You also may ask the question in the firebird-net list.



--
Best regards,
Pavel Menshchikov
http://www.ls-software.com/