
10-19-2013, 01:33 AM
|
Novice
|
|
Join Date: Oct 2013
Location: Co. Antrim, Northern Ireland
Posts: 8
|
|
Quote:
Originally Posted by fumei
Hi Fumei. Perhaps the users do not modify the template itself, but it would probably be better to have the template to build the document. ...so I distribute the template, and the end users will have to learn to open the template directly. Hopefully my macro can run, and produce the file content needed, but also produce a new file, leaving the template unaffected and ready for reuse?
The users select the items that are optional, and when finished that optional content is inserted. Rather than have ALL content in the new document, and the users have to remove anything. Yes
This certainly can be done, and by a variety of methods. The basic document, and a displayed userform to select the optional is one way. I intend to achieve this method, do you think this is the best method for me? I am not a pro level programmer but have completed entry level coding training and work as an applications engineer for a software company. My team expect this method, but after I have provided this project solution, I will also try to get buyin for a php website to do same. That way I also get global version control.
It takes good design and well thought structure, but it is very possible. If you really want to have all the content in and do a removal route, an efficient method is to have all of the "chunks" bookmarked. Removing them is easy. Interesting! Currently doc users have to trawl through the doc with click and drag actions to select and delete text to be deleted.
|
Thanks Fumei for the above tips. On one point though, my initial thought would be a double click on the template for the doc users to get going, but for my project you seem to have an idea that the code will work better if they open the template file directly. Is that right?
|