>>>use parameterized views - (and check the NoDataOnLoad property in the DE)
>>>then after you have a critiria just requery the view
>>>
>>>Arnon
>>
>>But what if I don't have a criteria? In my current update form, the user can browse the date by selecting next, previous, top, or bottom. They can also select find. Will I need to download the entire dataset to keep this functionality?
>>
>>What command can I use on the view to determine if a record exists? Using local tables I used SEEK. The user entered a claim number, and if it was found they could continue. How do I duplicate this on a view?
>
>Jeff
>
>here is some code I cut & pated out of one of my form's DataEnvironment.opentables() method:
>
>set multilocks on
>NODEFAULT
>llX = dodefault()
>*-
>if used('OrderHeader')
> select OrderHeader
> index on cCustID tag cCustID
> index on cCustName tag cCustName
> index on cDestID tag cDestID
> index on cShipID tag cShipID
> index on cStatus tag cStatus
> index on cTermsID tag cTermsID
> index on dDate tag dDate
> index on nOrderID tag nOrderID
>endif
>*-
>if !cursorsetprop('BUFFERING',5)
> wait window 'Table Buffering for OrderHeader could not be set.'
> *-
> return(FALSE)
>endif
>
>
>HTH,
>Tom


Since you upsized your application to SQL server, I think you should forget about navigation buttons, better use parameterized views.