>1) Should I create local views of the data required for each of the forms?
>2) Referential integrity...I have one parent table and 8 associated child tables with indexes set to the SSAN. Now I want to add the SSAN to each of these child tables (with 1 to 1 relationships. Must I have all these tables open when I add new personnel, create views with all these SSAN's, or will the information update to the child tables automatically?
>3) Are there any white papers concerning RI and a better explanation on
>its use?
>
>4) How do I go about installing the database and tables on our server and have the installation routine of my program be smart enough to know the database is elsewhere with the ability to search our server and write the "databasepath" to either my program ini file or main header file?
>And 5) Ultimately, what is the most LOGICAL way to accomplish this task??

I will try to answer most of your questions:
1. It's up to you to decide what is better suited to your needs: local views or whole tables opened with USE (basically it depends how speed you LAN is).
2-3. RI Builder will care about all standard referential staff, including opening and closing tables. If you are happy with standard triggers you shouldn't edit stored procedures manually.
4-5. Create configuration setting in your application which will check database file on stored path and prompt user to locate file if file doesn't exist. You can create application object with specific method to reset database path any time you go to Form.DataEnvironment.Init.