I am producing a Customer Acceptance Plan for a product manufactured by the
company for which I work. The product comes in several flavours, all of
which share common features and each of which has individual features common
to at least one, but not all of the others. For example,
product A is black, has a widget and a gizmo, has five interfaces, and
is battery operated.
product B is black, has two gizmos, has seven interfaces, and is mains
operated
product C is grey, has two widgets, four gizmos, has seven interfaces,
and is mains operated with a battery backup.
I am creating a form type document which our installers can complete on-site
and, based on a drop down box on the first page, I'd like to pull in the
relevant test cases for that particular model to that document.
Each test case contains a check box for 'passed', which is simply an
indication that the test has been executed successfully (failure is not an
option in this case; a single failure indicates non-acceptance by the
customer).
The unprotected document should contain ALL the test cases so that these can
be updated, but some way of identifying the application of the test case
would obviously be very useful.
I have considered using an access database to contain the text of the test
cases and building the document on the fly from there, but I'm wondering if
there is a better way. Interleaf, the Unix based word processor, allows
for such 'versioning' within a document, but all of our installers use
Windows NT laptops with Word 2000. To open an X-window connection to load
interleaf, they would need a broadband connection to corporate to support
the VPN so we need to provide a standalone solution, preferably contained in
a single file.
Does anyone have any thoughts on this?
Dave Burgess
reply to the newsgroup, or you can
email me at dave_burgess AT hotmail DOT com
There are probably a half dozen different ways to go about this; here are
two suggestions.
(1) Create a template that contains all of the test cases. Add an AutoNew
macro to the template, and have the macro display a userform. On the
userform you place a list box containing all the model designations, plus an
OK button. When the user creates a new document based on the template, they
first pick a model from the list and click OK. The code behind the button
then either (a) formats as Hidden all of the test cases that don't apply to
that model, or (b) deletes the cases that don't apply.
(2) As the inverse of the first method, the template's text doesn't contain
any test cases. It does contain the AutoNew macro and the userform. In this
version, the code behind the OK button inserts the test cases that do apply
to this model, either from Access or, more simply, from AutoText entries
stored in the template itself.
Here are some references to get you started with AutoNew and userforms:
http://www.mvps.org/word/FAQs/MacrosVBA/DocumentEvents.htm
http://www.mvps.org/word/FAQs/MacrosVBA/PseudoAutoMacros.htm
http://www.mvps.org/word/FAQs/Userforms/CreateAUserForm.htm
http://www.addbalance.com/word/download/index.htm#Tutorials -- download the
Userform template
If you need any help to get this up and running, c'mon back!
--
Regards,
Jay Freedman
Microsoft Word MVP Word MVP FAQ site: http://www.mvps.org/word
"Dave" <Dave_B...@hhoottmmaaiill.com> wrote in message
news:uaoOiRNVBHA.2256@tkmsftngp03...