Banking Database

Point value changed by question poster.

You will need to create 3 tables,
the 1st to hold just customer data (cust_id, name, DoB, etc),
the 2nd to hold the account data (account_id, type & amount) and
the 3rd to cross reference the customer table with the account table by id (id, customer_id & account_id).
Good luck

Improving on answer 1, I suggest that the account table include the customer number, and that the account number be an extension of the customer number, e.g. 33214-01 my regular checking, 33214-03 my m/m checking, 33214-07 my long-term savings account. The extension can then indicate the kind of account, assuming that no-one has two accounts of the same kind - in fact, even if someone has, that can be handled by allowing him only 10 of a kind an having 70 thru 79 for six-month term accounts, for example. Some real-world banks do this.

I would simply add the Customer ID as one of the fields in the Account table, and make one of the indexes based on Customer ID, Account No. as the unique identifier. You would obviously also need an index on Account No., but I would probably make ita unique index so that Account No.'s are not duplicated.

When you run your searches, you can use either index depending on requirements. The Customer ID/Account No. index needs to be built in early as so much of the coding will rely on that indexto provide the separation between accounts preventing customers from looking at or modifying accounts that aren't theirs.

Darryl

This question was closed by the author