I have been told over and over that I am much better off in developing a multi-use application using views for data input forms. I accept this advice as sound especially in protecting the original tables and for security reasons. However, I have never been very successful in using views on forms that use multiple views of both parent and child tables.

There are two approaches that have been suggested: 1) to duplicate all my tables as views, and then create my form(s) as I would using the views in place of the tables; 2) create one view incorporating all the tables I need for the form. The problem with the second suggestion is the view wizard won't allow more than two tables to be included in a view. I end up creating multiple views built on other views using a series of outer joins. This creates some problems in navigating through records.

The first solution would seem to make some sense, however when I try to create a form using more than one view I again have serious problems trying to navigate. This is especially true if I try to use a Pageframe with each page used to display information on a different view. Or even worse if I try display information from more than one view on the same page. [I know this is blasphemous on UT but what I am trying to do is mimic the way Access allows you to use subforms, so I can navigate through the records in my parent table or navigate through the records of a child in a single Parent record] I know there has to be a way to do this in VFP6.0.

If you can offer any help or advice I would greatly appreciate it. Thanks. --Lincoln