First off, I didn't say you didn't need the date field, what I said was you should RENAME it!
Secondly, are these FIELDS in the TABLE? Or are these the calculated fields in the QUERY?
TotalPrice currency (Homeprice+LotPrice+SitePrep+ContractExtras ect.)
Deposit currency
PropMtg currency (amount of loan)
CashReq currency (TotalPrice - PropMtg)
FivePerDeposit currency (5% of TotalPrice)
BalanceToClose currency (TotalPrice - Deposit - FivePerDeposit - PropMtg)
If these fields are in the table, you should remove them; storing calculatd fields breaks 3NF (if you don't know what 3NF is, read
'The Fundamentals of Relational Database Design'). There are also other aspects of your table structure that break 3NF (for example, ContractExtras, ContractExtras1, etc.). Secondly, you have PERSON information stored in the CONTRACT table. Again, breaks 3NF.
I would first suggest that you review your table structure and get your database to 3NF before continuing with this project. You will find that if you do not it will become harder to extract the information you need.
Just from reviewing this table I would expect a 3NF design to be similar to:
tblPersonInfo
PersonID (PK)
LastName
FirstName
(any other information about the PERSON)
tblProperty
PropertyID (PK)
LotNum
BlockNum
SecNum
SubDivision
(any other information about the PROPERTY)
tblContract
ContractID (PK)
PersonID (FK to tblPersonInfo)
PropertyID (FK to tblProperty)
(any other information about the CONTRACT)
tblContractExtras (this table allows you to have UNLIMITED number of Extras for each contract instead of the 4 in your structure)
ContExtraID (PK)
ContractID (FK to tblContract)
ExtraAmount
I'm not sure where in this model some of your fields should go, but this will give you some idea of what your structure should look like. NONE OF THE CALCULATED FIELDS SHOULD BE STORED IN THE TABLE!!! All the calculations should be done in queries.
Leslie