Alan,
My $.02 US - I always ask the client, and drop them on the form if they're wanted. My last SQL-Server project didn't have them, for all the reasons your other messages gave, but the users said they often brought back all the records for a group of projects (yes, this was "The Project Project") and liked to scroll through them in chronological order without having to flip pages from a grid. The buttons gave them a full screen of data with each refresh.

Barbara

>I'd be interested to know what the FoxFolk out there think of navigation controls. I've been using them for years now, either as toolbar buttons or on the form itself, and they have corresponding Next, Previous, Top and Bottom methods within the frameworks I have used.
>
>But who actually uses them? I've recently done a (very small) survey amongst a few database uses I know and very few actually use them. Most users pick a required record via a grid and/or criteria entered to produce a SQL subset. Usually they can see all they want to in the grid and it's no problem to double-click on a row to display full details relating to that particular record.
>
>I've read that navigation controls are out-of-favour for client-server applications, where as few records as possible should be selected.
>
>What do other developers think?
>
>Alan