Hi Carolyn,

It was I who suggested you come here for help but now that I've read your
request more carefully (and went back and looked at the thread in
microsoft.public.access) I've changed my mind...  Sorree!

When I read your request before it seemed that the Treeview and ImageList
controls working together would do what you want - I still believe that they
would but now I believe it would be more time and trouble than you need and
it might have pushed your application in a dysfunctional direction.

Rather than me referring you all over the place, lets settle on a newsgroup
to work out your issues.  I think that microsoft.public.access would do or
even microsoft.public.access.forms but lets first explore what you're doing
and then settle on a newsgroup. :-)

At the time you're going to click a "Word" button will you already have one
or more records on a form (or subform) with some contextual info showing?
From your posting, I believe that you will.  Assuming that's so then

You'll need an additional field in your table to hold the Word document name
associated with the record.  You will have to work the issues as to the
location of the Word documents.  You can have some common root folder for
the .docs or you must include the full pathname for each document in the
table.

You need to decide whether you'll Shell() to Word or if you'll use
Automation - Look up Automation in Help.  I've had synchronizing issues with
Word and Automation and in one application the only way I could get things
to play together cleanly was to open a Word session when I started the
Access application and only closed it as the last thing before closing
Access.  Creating, printing and closing Word documents was no problem.

As to the "Word" command button I'll leave it to you to find a Word icon to
use - you should be able to one easily.   See if you can work out how to get
the icon on your command button.  The code you'll want behind it will be
determined by which path Shell/Automation you take.  I think you'll probably
take the Automation path.

You can decide where you'd like to continue this dialogue.  We could easily
go back to your original thread from a week or so back or we can continue
here..  Just this once I'll welcome an email to work that issue.  In any
case, the above posting should be a part of where we pick it up.

My apologies for sending you on a wild goose chase.  Hang in there, we'll
get it.

hth