Greetings!
The main problem and simulteniously a great benefit of the job described is missing of clear task specification.
Despite many implementation aspects, now you have the BEST MOMENT to design the application in a way that will really save time and add clearness for your business procedures... And this is my lovely starting point!
So, first we need, clarifying details and considering ideas, to come to the "application of your dream" designed on paper - this is what I mean specifying milestone 1 of the progect.
Then.. I would just implement what we'd agree about - milestone 2.
Implementation could take even less time than task specification.
Regards,
Sergey
P.S. As far as I have some remaining characters in this field, I'll start discussion...
>>> Store/shortcut quick and easy access to documentation for each client file and display them in logical order;
You have 2 options for storage engine for your papers:
1) File System - you establish rules for naming and places to store all papers per client/contract/etc, use Word/Excel/whatever to design/edit/print them, the database just manages hyperlinks to these files - it is very flexible if nice design is needed, if many changes to templates occur etc
2) MS Access - you don't keep any files, every document is a data+template, both stored in Access - this is like you mentioned for Proformas autogenerating
Also, there is a 3-d way: f.e. nice Excel file is a template that uses data directly from Access.
...