A stored procedure that I would like to add to LLBLGen Pro does not show in the New Stored Procedures dialogue box when I click Add New Action Stored Procedure Call. I tried Add New Retrieval Stored Procedure Call just in case, but it does not show up there either.

It is a complex stored procedure for sending an email message. There are no result sets, apart from the possibility of an error message output with SQL's PRINT statement: I'm not sure if that counts as a result set or not. Has that got something to do with the problem? I would be quite happy to not capture the error message if there is one: checking the stored procedure's return value for success or failure would be good enough. I could stop the stored procedure from PRINTing error messages, or use SELECT instead of a PRINT, if either of those would solve the problem.

The only other thing I can think of that might be unusual is that the stored procedure calls a hierarchy of other stored procedures, including one that PRINTs the error messages.

Did you refresh the catalog?

No, I did not refresh the catalog. But now I can see that I made a stupid mistake. The stored procedure must have been in the New Stored Procedures dialogue box all along, even without refreshing the catalog. I must have missed it because its prefix was being stripped off in the Call Name column. The prefix is the one specified in Pattern to Strip off the Stored Procedure Names in Project Properties.

I am using LLBLGen Pro 2.0.0.0 Final (Feb 14th 2007). I notice that the under the Project Menu Item, "Add new Action Stored Procedure Calls", "Add new Retrieval Stored Procedure Calls" and "Add Typed Views from Catalog" menu item are all grayed out.

How can I enable them?

Thanks

Derek

Sorry, I forgot to check the Stored Procedure and View on the refresh catalog form. it works fine after I check it and I am able to add stored procedure calls.

Derek