on 2012 Feb 09 1:41 PM
Are there any known issues when using the EnityConnection and doing a storedprocedure call with an ExectueNonQuery()? This call is always throwing an 'Object reference not set to an instance of an object'. But looking at the stack the error happens on a System.Data.EntityClientEntityDataReader.Close(). I'm wondering if it is a bug since two steps earlier in the stack it issued a System.Data.EntityClient.EntityDataReader.Dispose(). When walking through the code in debug the error is thrown inside the ExecuteNonQuery() call. However, the code in the stored procedure is executed. As a work around I have put a try/catch around the ExecuteNonQuery() call. I am using Visual Studio 2008 and the 3.5 framework, connecting to Sybase 12.0 using iAnywhere.Data.SQLAnywhere.
Request clarification before answering.
User | Count |
---|---|
53 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.