Hopefully, this won't be such an issue in the future with LINQ.

 

My sproc contained references to user-defined functions as well as temporary tables. After commenting out these items and re-running the object mapper, I was able to succcessfully generate the entity. I then uncommented the necessary parts of the sproc and everything seems to be fine.

 

I'm curious, is this an issue with DevForce or is it something that's out of your hands in SQL Server? And if you can, do you plan on fixing it at some point? It's not a show-stopper by any means, but it could get irritating after a while, every time you open the object mapper...

 

Thanks again for your help.

 

 

 

The Object Mapper looks at your stored proc, and tries to figure out its input and output parameters.  If it can't figure this out, it reports "Schema Not Found".  Characteristics of your stored proc that will cause the Object Mapper not to understand the output shape are (among other things):

 

(1) Temporary Tables

(2) Dynamic SQL

(3) HAVING clauses

 

The workaround is straightforward.

 

(1) Create any stored proc that gives the right output shape

(2) Map the Stored Proc query using the Object Mapper

(3) Replace the "dummy" stored proc with the real one

(4) When you use the Object Mapper, you must be careful not to regenerate entities.  Otherwise, you will get the same "Schema Not Found" error.

 

However, every time I select the sproc from the "Add Unmapped Tables/Stored Procedures" window in the Object Mapping Tool, the entity is added to the class list with a red exclamation mark next to it, that reads "schema not found" and the class detail is unavailable.

 

This only appears to happen for some sprocs - others I can add without any problem.

 

I can't seem  to find any differences between sprocs that work and those that don't. Does anyone have an idea of what migh tbe going on here?

 

Thanks!