To Page or not to Page - That's the question
-
My data access experience in .NET is limited to a data set, a data reader and a scalar, and in VB6 it was of course record sets. Now I am told paging is the best - for Forms applications. We have a Citrix environment and the data sets are quite small - pre-filtered via parametrized stored procedures. Which is best Paging or Non-paging - and why?
the confused are confused beyond confusion
-
My data access experience in .NET is limited to a data set, a data reader and a scalar, and in VB6 it was of course record sets. Now I am told paging is the best - for Forms applications. We have a Citrix environment and the data sets are quite small - pre-filtered via parametrized stored procedures. Which is best Paging or Non-paging - and why?
the confused are confused beyond confusion
-
What does the person that pays you want?
xacc.ide - now with IronScheme support
IronScheme - 1.0 alpha 1 out nowThat is the problem. We are busy with a Developers Readiness Program to move from VB6 to .NET (C#) and we have to rely on a consultant who is very proficient in his work. Unfortunately our team does not have the knowledge to make a judgement call. Some of use have more experience in C# development but not enough to say Yes or No, but more or less understand the complexity of some of the topics involved. I'd like us to see us move fast with the conceptual knowledge we have and build the "better" systems later into the framework - if it is needed. I also understand "later" can become "never". We know and understand the "de facto standard" to fast track us, but now Paging is recommended and as I understood from the consultant not that easy. I say, let's have both options and one as architect will decide based on the problem which to choose.
the confused are confused beyond confusion
-
That is the problem. We are busy with a Developers Readiness Program to move from VB6 to .NET (C#) and we have to rely on a consultant who is very proficient in his work. Unfortunately our team does not have the knowledge to make a judgement call. Some of use have more experience in C# development but not enough to say Yes or No, but more or less understand the complexity of some of the topics involved. I'd like us to see us move fast with the conceptual knowledge we have and build the "better" systems later into the framework - if it is needed. I also understand "later" can become "never". We know and understand the "de facto standard" to fast track us, but now Paging is recommended and as I understood from the consultant not that easy. I say, let's have both options and one as architect will decide based on the problem which to choose.
the confused are confused beyond confusion