Click here to Skip to main content
15,893,722 members

Comments by stackhoover (Top 14 by date)

stackhoover 8-Oct-11 8:51am View    
Thanks anyway!
PS: I commented that "=Nothing" a long time ago.. ;-)
stackhoover 8-Oct-11 8:29am View    
Tried that...The parameters end up neat as Parameter.Item 2-5 with correct name and value (Item 1 is the @RETURN_VALUE). The following line executes without complaints:
Set rst = Cmd1.Execute()
But, no trace of the command in the profiler...
The whole thing crashes in this line:
RVDATA = rst.Fields(0).Value
A lot of "Operation is not allowed when object is closed" in the properties of the rst. ;-(
I have also tested the whole udf using a plain text sql command, and not an command object with parameters, that does work! So the bug is not in the connection nor in the function on the sql server. I'm getting nuts!
stackhoover 8-Oct-11 8:05am View    
When I use adCmdStoredProc the command does not arrive at the server, at least the profiler can't see it. When i disable adCmdStoredProc I see "exec dbo.D100601RVDATABearingAllow" arrive at the server, but I also get the errormessage back that the variable @Fastener was not supplied....
stackhoover 8-Oct-11 7:57am View    
Hi,
I have just checked that. It's ok. Just before I execute Cmd1, in the debugger the Command text is: "{ call dbo.D100601RVDATABearingAllow(?, ?, ?, ?) }"
Are the question marks ok there? And is "call" correct? In the management studio the function only works with SELECT. Thanks for your help so far!
stackhoover 8-Oct-11 7:52am View    
Hi André,
when I try
SELECT dbo.D100601RVDATABearingAllow(2348,2,'f','SS')
directly in the management studio, the function returns the correct result.
Do I have to define a parameter of type adParamReturnValue to store the result in?