Hi Rick,

You could store the last primary key either in a table or registry on each user's workstation. When they open the form, requery the view using the stored primary key. This does not mean the other filter conditions cannot be applied, but it simply means that you set all the other search conditons to BLANK.

e.g. If you have a customer table and want to search on Last Name, First name, address and even the primary key, your view would look something like

SELECT * FROM customer ;
WHERE cid LIKE ?vp_cId ;
AND cLastName LIKE ?vp_cLastName ;
AND cFirstName LIKE ?vp_cFirstName ;
AND cAddress LIKE ?vp_cAddress

Now at different times you only need to set the right values for the View parameters and simply REQUERY() the view.

>My users want to see the last record entered into the table whenever they open the app. The last record entered(maintained as a primary key value) is maintained in a seperate table for the users to keep track of.
>So, to show the last record in the view, I need to do a 'Locate' or 'seek'
>My question is, should make the view parameterized based on the p. key value?
>But, if the user searches the table on other fields(which occurs often), should I change the parameters of the view??
>
>Also, Is my situation too difficult to use Client Server??
>
>P.S: The users do lot of locates while using the app.
>Hope I'm clear with my question.
>
>Thank You