Support forum for Huagati DBML/EDMX Tools
3/31/2011 3:56:30 PM
Dave Ambrose
Posts: 2
|
I have a stored procedure that uses a couple of temporary tables. The stored procedure works when I run it and returns the result set without error.
When I run the sync tool however, I am given this error in the output window and while the procedure IS added to the dbml file, it doesn't have the correct result type and thinks it's just returning an int:
An error occured when checking the procedure/function dbo.portfolio_view_annual_yield_comparison for changes.
Warning: executing stored procedure or function portfolio_view_annual_yield_comparison failed: System.Data.SqlClient.SqlException: Invalid object name '#returns'.
Completed updating the Linq-to-SQL classes from the database.
Is there anything I can do to get it to sync this stored procedure with the rest?
|
|
0
• permalink
|
4/14/2011 11:36:14 AM
Ketan Shah
Posts: 6
|
I'm getting the same problem while evaluating the software.
I suppose the simplest workaround for this is to temporarily change the stored procedure to use actual tables and NOT use temporary tables though I don't fancy the idea of doing this everytime I want to do a compare.
|
|
0
• permalink
|
4/14/2011 2:55:22 PM
Dave Ambrose
Posts: 2
|
Note that this isn't actually a problem with the Huagati software, you'll get that same error if you try and manually drag that stored procedure into your dbml file from the server explorer, so it appears to be a Microsoft issue with regard to that, fwiw. Overall I'm still very happy we bought the software and use it multiple times every day, usually without issue.
|
|
0
• permalink
|
4/15/2011 3:32:15 PM
Ketan Shah
Posts: 6
|
Ldaco wrote:
Note that this isn't actually a problem with the Huagati software, you'll get that same error if you try and manually drag that stored procedure into your dbml file from the server explorer, so it appears to be a Microsoft issue with regard to that, fwiw. Overall I'm still very happy we bought the software and use it multiple times every day, usually without issue.
You've actually reminded of the solution to this. You need to add the following (temporarily) to the start of the stored procedure while adding it to LINQ-to-SQL or doing a Compare, etc.:
SET FMTONLY OFF
No more error but you have to remember to remove it afterwards.
|
|
0
• permalink
|