On your "detailed" form, you could bind the controls to a view, instead of a table. So, instead of "seeking" a record by ID, you would SQL Select it into a cursor/view and then bind the controls to the view.

HTH.

>I have been programing with VFP for awhile now and my framework is working fine with VFP databases.
>Now I want to play with the big guys and do client-server application with VFP 8. I will primary use MySQL for the database.
>Now, I tested pass-thru commands and I think I understand the idea.
>
>My applications basicaly have 2 types of forms:
>1) A screen where the user can browse through the clients (for example) and search for a particular record. For this one, it will be easy to move to client-server because I am alreay using the result of a SELECT, into a cursor, and I manually make the grid record source ok. So I don't see too many problems there.
>
>2) When the user open a particular record (1 client for example), I open another form with the data of this particular record. This form receive the record ident (key) in a parameter and do a seek on the table to get the proper record. ALl the fields are bounded. So when we are in development mode, it is easy to drag the fields from the table on the screen.
>Now I wonder.... In a client-server development mode, what is the best approach to design this screen. Do I have to manually assign the record source of each single field ? It seems very ineficient to me...
>Any suggestion ?
>
>Thanks
>Eric