Hi again Chris
If I understand the basic concept here as you describe it, I believe the most straight forward solution would be to automate the Word document production with VBA from the Access database. That's somthing that, in principle, is pretty straight forward.
An alternative method (or an additional feature, if you felt so inclined) would be to use VBA in a Word addin to control and output the data from Access and populate the document.
Since VBA is part of each app there's no software to buy, the code is integrated and because the code has a host application, deployment is fairly straight forward
A third way (to hijack one of Tony Blair's favoured clich?s) would be to knock up an app in .NET (VB, C# or a mixture of both) that gets the user input, gets the data, runs some code-behind to bring it all together and passes it to a document it creates. The .NET approach is the one that offers the greatest range of choice and flexibility when it comes to how you design and distribute the finished product. You're running this from a server, so the entire app could remain server-side and you could make a web-app for the user interface, so the only thing needed client-side would be a compatible wed-browser. You could output the document in a number of ways but if it needs to be edited later in Word, the user would need it installed (tho it could be done as a background process). Any future development or maintenence of the app would be more convenient. For example, if you later needed to port the database over to SQL, you'd just need to deal with that aspect of the code base.
The down-side of .NET? Well there's certainly a lot more to learn. Depending on your experience, the learning curve is steep for quite a while and will probably eat up a lot more development time that the VBA options. The higher price, in all respects, would be more of a long term investment in the product and if you really don't want to make a career out of it, it seems like quite a big task.