>>I'm having trouble finding any decent documentation on creating views (and exactly what they are). I need to create some views from multiple tables (my wonderful "multi-table grids") to be used within an application consisting of mostly forms.
>>
>>I have to relate one table to several others to come up with the necessary fields for my forms, and these need to be updateable.
>>
>>An example is my Contacts table which contains codes for PersonID (to connect them to a Person table which contains first, last etc.), AgencyCode (to relate to the Agency table... to get the full name of the Agency the person works for) and PositionCode (to relate to the Position table which contains the titles/positions the people hold). I can create these relations (minus Agency for now) in the VFP command window with:
>>
>> use contacts in 0
>> use person in 0 order persid
>> use position in 0 order poscode
>> sele contacts
>> set relation to persid into person, poscode into; position
>>
>>I tried using the Menu->New->View Wizard, and also the View Designer within my Database Designer, with no luck. Also, after creating views and saving them, I can't find them to modify/reuse them.
>>
>>Any suggestions or pointers to decent explanations of what views are and how to use them with multi-table relations?
>>
>>Hope you don't mind the novice questions.
>>
>>TIA
>
>I sure hope that they don't start having 'EXPERTS ONLY ALLOWED', what would the point of having this site if everyone knew all the answers?! ...and they's have to revoke my membership to-boot!

Thanks for the kind words. It's easy to feel lost out here ;^).

>Have you set up a database with all your tables and relations yet? Once you do, you can add your views to the database. I have not had any problems finding them once they are in.

I have created a database with my tables (about 50) and relations. It's pretty much a spider web of relations and I have encountered problems with too little memory errors (16MB). I found some info on the Microsoft Site about views which is helping. Plus it looks as if with views I can use 'subsets' of my tables in smaller dbc's which can just contain a few local views necessary to specific forms, thus getting around the problem of a table only belonging to one database (which I was trying to get around since I wasn't able to keep all tables in one dbc due to memory errors). I'll keep plugging away. Thanks for you response. (I hate working on projects solo)