Trying to test a stored proc in EDB Manager, but can't figure out how you do it.

Execute Procname();

Call Procname();

all return 'No statement found to be executed'. A SELECT statement works fine.

So how the do you test a stored proc ? We've spent hours trying to get this thing to work.

Clicking the Execute Procedure produces no result set, and no error message.

Olybino


I suspect that your stored procedure has no result, possibly has no parameters.

I just tried here. Clicked Execute Parameter and right click parameter name in the tree and execute parameter and double clicking the parameter name in the tree. In all cases I had a form presented to enter parameters and a second form presented with the OUT parameter

Can you post the code of your SP please

Roy Lambert

Many hours after I posted that, we got the proc working. The lack of either documentation or complete examples was really frustrating. Yes, the null result was from no input parameter because it took a very long time to realize that I needed to actually click the 'Set Parameter Value' button in the manager, rather than just click Ok after filling in the field line.

Anyway, it does work now, but coming from Interbase it's really very different, and Tim's SQL manual is of very little help in learning how procedures need to be constructed for EDB.

Olybino


<<Anyway, it does work now, but coming from Interbase it's really very different, and Tim's SQL manual is of very little help in learning how procedures need to be constructed for EDB.>>

Tim's manuals do not even touch on EDBManager, they are very good for ElevateDB both at Delphi level and SQL level. The best thing is that if you need help post in the newsgroups with enough detail that we don't need to guess to much.

The SQL is pretty much according to the standard with some enhancements which are covered in the manual. If you stick to the standard you shouldn't have any problems. Learning to use EDBManager effectively only comes with practice (I know I've been using it for ages and still occasionally find hidden features). The approach I use for SPs is to develop as a stand alone script in EDBManager and convert when working to an SP. This means that you can access the limited debugging features built into EDBManager. If you have specific questions or how tos post them here and I'm sure someone will try and help.

Roy Lambert