Bonnie,

I agree with your points about lemeting the displayed rows, & it's there in the application (under dev. now). But using the Next button is additional option in the application for the user whether the user used it or not (& it will be used by management).

But my concentration was about what you said "Client/Server applications", & I think you answred the question.



>Ahmad,
>
>It really all depends on your application, but for the most part, I doubt if user's like to click on a Next button constantly just to find a row. Typically, the choice is narrowed down and presented in a list, combo or grid ... so they can then have the option of choosing a specific record to view and/or edit. By narrowed down, I mean present a list by a date range, alphabetically one letter at a time or by some other criteria so that you bring down from the server a manageable number of rows for the user to choose from.
>
>However, if you application is such that the user works on records sequentially and the user actually *does* need to click Next to get the next record each time, then yes, you could do something along the lines of what you suggested.
>
>~~Bonnie
>
>
>>Wait a menet Bonnie, I think I have to stop here and invite you for a cup of tee :-)
>>
>>How is that.... ?
>>ADO.NET works as disconnected dataset, & if I need to do what you are saying then,
>>I have to send the first 100 rows for example to the dataset in the first time and when the user reaches the row 100 and he still clicking "Next" button I have to clear my current dataset and go back to database and get the next 100 rows and so on ... is this what you mean ??
>>
>>
>>
>>>Ahmad,
>>>
>>>If you're not displaying the data in a grid or something similar, then you don't need to get all the rows. The user can still do the Next/Back thing ... you just have to go back to the server and grab the correct data each time. Client/Server applications have always had to use this type of paradigm. You're just not used to it. <g>
>>>
>>>~~Bonnie
>>>
>>>
>>>>Bonnie,
>>>>
>>>>The current number of rows I have now is 65,000 + somthing !!!.
>>>>
>>>>And in this case the user will loss the feature of moving "Next" & "Back" in the dataset, and replace it with the SELECT statment to point directly to the wanted row.
>>>>
>>>>But, my point is... in old languages and even VB6, they had SEEK method to search for any indexed column, and FIND method for not indexed columns, in .NET I don't see any advandate in keeping only .FIND method and limit it to work only with PK!!