To all that reads this posting, greetings

First off I want to thank everyone on the responses I've received so far during the creation of my project.
Eventually, my data will reside on our LAN. Each workstation will have a copy of the program installed on their computer. IMHO I should create local views of all my data now and work from them, but this opinion is derived from the little experience I have with VFP so far. So I need some guidance here. Views, Data Environments, Classes, etc. I know a lot of people don't like listboxes for table navigation, but that's what is requested and I must comply. But I also use a toolbar for navigation. On this form I have set my DE using the actual tables. If I bind the listbox to the data and add a record it naturally generates an error, thus I was advised to create a cursor for the listbox. (Now I can make the program behave like my other version I created in 2.6, but I don't want that, if I'm going to learn this program I need to start comprehending and utilizing the capabilities it's famous for.) So I'll tell you what I want the program to do so you'll understand where I want to be when completed.
1) I need security, and I have successfully implemented Arnon's encryption routine for passwords. But I do need to turn if off for a new installation.
2) My main form for inputting personnel has a listbox tied to my data displaying alltrim( person.lastname)+', '+substr(person.firstname,1,1). Dbl click the name and the text boxes refresh contents of that field. When navigating with my toolbar I want the list to reflect current record. It does this with no problem. However...
3) Adding records. Don't want to Append if there is a record marked for deletion. I want to recycle that record, but I generate an error because of my key field(SSAN). (I'm in the military, this IS a good KEY). Binding my data to the listbox will generate an error because it is trying to access a record that's not there(yet). After adding record to this parent I add the key to 6 other tables, I need to recycle those deleted records too. More errors! Referential integrity. I added code to my stored procedures and created a function AddtoAll utilizing INSERT INTO for my cscading insert. (Thanks for that one Edward)
4) We track immunizations, and boosters are due anywhere from 6 months to 10 years. My old way of storing these records was each person had only 1 record. If we decided to track an additional record, we go to the table that stored the shot name and frequency it is due. We then (believe it or not) redimensioned our other table to add those new fields. I think having 1 table with the shot name and freq, and a 1 to many in the immunizations table and just create 1 record for each shot. (I really want opinions for this one) If I do a 1 to many I an going to have to create a new record for each distinct record(by SSAN). Should I do this automatically or only when I select that persons record? The first is more practical for me due to our mobility committments, that way we can report on personnel who are not up to date.

I know I am repeating many of my questions previously posted. But as you all can see, my refinement seems to go in stages, which means if I don't get on track now, I'll be here for years going backwards! I have my plans, they just don't quite fit in OOP world...Yet. :-( I believe I need some sort of flowchart to record my R&D so I can follow a logical set of steps in accomplishing my task. I need a plan! Sorry if all this is so basic to all of you, but you're the only VFP family I got! <g>

Thanks for the advice in advance