Thank you for your response.

>Just a few rather general points that might help: (all points are related to local views only)
>
>1. My understanding is that VFP can reliably update only one table in any given view. If, within a single container/business object you need to update more than 1 base table, you'll have to use separate views. OTOH, in some cases you need to look at information from related tables in a read-only fashion while you make changes to another. Views work very well for this.
>

I will need to contemplate the implications of this.

I haven't gotten to the point of trying to update. I'm still trying to get the forms to navigate through the appropriate records using "next" and "back" buttons. The behavior is very odd.

>2. The View Wizard is simply a user-friendly front end for the CREATE SQL VIEW command. That command can create some incredibly complex views by directly using SQL syntax. You can also check out Erik Moore's eView utility in the Files section.
>

I did download Moore's eView and will try experimenting with it

>
>3. Just a very general comment here - linking child objects or forms reliably to a parent is a non-trivial process. Simplifying this is one of the strong points of all of the commercial VFP frameworks. Have you looked into them at all, or are they not suitable for your needs?
>

I am not familiar with any of the commercial VFP frameworks so I'm unsure of their suitability. Are there any you would recommend my checking out?

Thanks again. --Lincoln