Hi - I'm not sure where to post this, if this isn't the right place please let me know.
We have an application using WPF/RIA services and an MVVM framework. We called stored procedures in SQL to get data through our model.
I've found an issue that I can't explain and so don't know how to fix. What we are seeing is that the results being returned by our stored procedures when I run them directly in SQL Server Management Studio don't match what I see in the application. In this case, we are displaying the data in aRadGridView, but I can look at the data when it is returned in the context and it's wrong there too.
The problem is that not all the records I expect to see are there. For example, in one case my stored procedure run directly from SMS returns 251 rows, the grid in our app is displaying 20 of them, and I see those 20 rows in the results when I look running in Debug.
Are there settings that limit the amount of rows that are returned? In some cases, there are a lot of rows, but what we've found in the past is that the app times out. I'm not sure where else to look.
Any help would be appreciated!
Lisa
We have an application using WPF/RIA services and an MVVM framework. We called stored procedures in SQL to get data through our model.
I've found an issue that I can't explain and so don't know how to fix. What we are seeing is that the results being returned by our stored procedures when I run them directly in SQL Server Management Studio don't match what I see in the application. In this case, we are displaying the data in aRadGridView, but I can look at the data when it is returned in the context and it's wrong there too.
The problem is that not all the records I expect to see are there. For example, in one case my stored procedure run directly from SMS returns 251 rows, the grid in our app is displaying 20 of them, and I see those 20 rows in the results when I look running in Debug.
Are there settings that limit the amount of rows that are returned? In some cases, there are a lot of rows, but what we've found in the past is that the app times out. I'm not sure where else to look.
Any help would be appreciated!
Lisa