>>It seems that this might be similar to doing a PO. Master table for policy info and child table for the detail (i.e. pages)
>
>Each account can have multiple properties. So each page would duplicate borrower information name, such as name and account number but the property information would change. What is the best way to keep track of the number of pages? How do I keep track of where each page is in the order? My main concern is when deleting or adding. If I hardcode a page number into each page then I have to go back and edit each affected page.

Let's see if I understand what you mean.

1) You have a Customer file whith general info. Each customer has an Account Number.

2) You have a properties (pages?) file which has a foreign key to the customer (i.e. the account numeber). Index on the foreign key for speed. Each property receives a number as it is created which has no special meaning, but that you can use to determine the order in which they were created (i.e. previous/next).

3) Instead of keping track of the number of pages you actually count them each time you need to know.

Hope this helps,

Alex