Silvio,
I don't know how familiar you are with relational database design, but this is the number one rule:
First Normal Form (1NF): A table is 1NF if every cell contains a single value, not a list of values. This property is known as atomic. 1NF also prohibits repeating group of columns such as item1, item2,.., itemN. Instead, you should create another table using one-to-many relationship.
So, in your rental file records you should
not have multiple names as fields, but rather each name should be a record in a related table.
RentalID, Last, First
You can have any number of records in the name file with a minimum of one. This eliminates a lot of wasted space in the rental record file and it allows you to search for any name in the person file; just index on upper( trim(LAST) + trim(first) ). Then you can search for any name in any rental with one simple seek().
Alternately, in your case you could leave the renter's name in the rental file and just put all the "guests" in the related table. This would make it more difficult to get a list of renters plus guests though.
For more about relational database design see:
https://www.ntu.edu.sg/home/ehchua/prog ... esign.htmlUnrelated to your current need, but note that you can create a method in the Rental Object (singular) class that returns an array of all the guests on that rental which you can then call from the object.
oRental:GuestList() // returns a list of people for that rental
This method would open the guests database and find all the guests on that rental and return the list as an array. This
encapsulates the list as part of the rental object.