This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I have ODP 11g installed in VS2008 and I have a connection setup to my Oracle database in the Server Explorer. When I try to drag a stored procedure from the Server Explorer onto the LightSpeed designer for the data model it doesn't do anything. The designer surface stays blank, the message window doesn't report any errors and I get no other feedback. The designer indicates that it has changed when you try to close it but no changes are actually saved into the file when I look in the generated vb file. If I drag table on it's works as expected but not stored procedures. Am I missing something? I have the relevant <dependentAssembly> binding setup up by the way. Thanks, |
|
|
PS : Nor doesn it work when I use the Microsoft Data Provider for Oracle (it does exactly the same thing). |
|
|
From the fact that tables work I don't think this is a driver issue, so it is probably something to do with the specifics of the stored procedure. The metadata around stored procedures is a lot weaker than tables so we have to do some heuristics (or "guesswork" as we prefer not to call it) to figure out the returned schema. I suspect that our heuristics are unable to handle your particular procedure for some reason. One possibility is that the stored procedure doesn't conform to LightSpeed's convention for Oracle sprocs, which requires that the results be returned through a out parameter of type ref cursor named "results." If this is the case then let us know because we should be producing meaningful diagnostics in this case rather than just failing. Otherwise, could you post the stored procedure please? Thanks! By the way, if need be you can always set up the sproc manually by dragging a Select Procedure from the toolbox and setting up the appropriate return type and parameters. More laborious than dragging, obviously, but it provides an escape hatch if the designer can't cope with a particular sproc. |
|
|
Thank you for the speedy response. I didn't have the OUT param named results - as soon as I changed it everything worked as expected. Many thanks, Rob. |
|
|
Thanks for letting us know about this. I've fixed it so that in future it should display an explanatory message in the Output window if this happens, so it should be a bit clearer what's going on! |
|