Dave,
I'm pretty familiar with Word automation, but the Outlook object model is
Greek to me. I think, with Sue's help, I'm gonna get this solved.
Thanks.
--
Dale
"David C. Holley" wrote:
> It looks as if you're well on you're way to getting at the information, but
> you also have to get it to print. I do not believe that Outlook has any sort
> of inherent report functionality that you can customize.
> But, in the same way that Outlook can be Automated, you can automate Word to
> capture and format the information and then print it. Also, you should be
> able to do it in such a way that it prints without the user ever knowning
> that Word was invovled. When you get to that point, you'll want to hang out
> in a Word newsgroup. I've done it myself but it was one time 5 years ago.
> Not to difficult over all.
> "Dale Fye" <dale.fye@nospam.com> wrote in message
> news:32513C05-6E36-4EDD-B743-91BDB40733CE@microsoft.com...
> > It just prints the basic information (addressees, subject, dates/times,
> > body
> > of the message.
> > Besides, he needs to get this into some form of Word or PPT document, so
> > being able to print it does not help!
> > --> > HTH
> > Dale
> > "David C. Holley" wrote:
> >
> >> What happens when you open the Meeting Item and click print? I seem to
> >> recall that they meeting attendee status used to appear there.
> >
> >> David (hint)
> >
> >> "Dale Fye" <dale.fye@nospam.com> wrote in message
> >> news:A10CAAA5-9698-4EA0-AC33-3ADB7EE42D10@microsoft.com...
> >> > Actually, Dave, I would prefer to do it in Outlook. But when I
> >> > couldn't
> >> > figure out how to get a simple printout of the meeting request
> >> > recipients
> >> > and
> >> > their response, I went to Access (my area of expertise) to see whether
> >> > I
> >> > could find a field in either the calendar or mail item collection that
> >> > had
> >> > that information, but did not find one. Thats when I posted my note.
> >> >> > --> >> > HTH
> >> > Dale
> >> >> >> >> > "David C. Holley" wrote:
> >> >> >> Regardless of the fact that you're trying to do this within Access,
> >> >> this
> >> >> is
> >> >> an Outlook Automation question and thus appropriate for the Outlook
> >> >> newgroups. Automation is simply code within one application that
> >> >> reaches
> >> >> out
> >> >> to work with another. Its irrelevant if you're using Access, Word,
> >> >> Excel
> >> >> or
> >> >> Power Point, its all Outlook.
> >> >
> >> >> To that end.
> >> >
> >> >> Are you storing information in the Access database on the meeting?
> >> >> Where
> >> >> does Access come into play with the Meeting Request? Are you creating
> >> >> the
> >> >> Meeting Request in Access to begin with?
> >> >
> >> >> Yes it is entirely possible, but you're trying to do this from within
> >> >> Access
> >> >> you have to locate the MeetingItem first. How you do that depends on
> >> >> how
> >> >> the
> >> >> Meeting Request is being created to begin with as there are ways to do
> >> >> this
> >> >> that are easier than others.
> >> >
> >> >
> >> >> "Dale Fye" <dale.fye@nospam.com> wrote in message
> >> >> news:19F7EC8D-5466-43F1-B92B-4E35B364FACE@microsoft.com...
> >> >> >I have cross posted this to the Access-General, Outlook-General, and
> >> >> > Outlook-programming-vba news groups to expand my pool of expertise.
> >> >> >> >> > I have a co-worker that wants to be able to print out the list of
> >> >> > invitees
> >> >> > and threir responses to a meeting request (what is visible when you
> >> >> > select
> >> >> > the "Show - Tracking" ribbon option in 2007. We cannot figure out a
> >> >> > way
> >> >> > to
> >> >> > print or even copy this info. He has more than two pages of
> >> >> > invitees,
> >> >> > and
> >> >> > would prefer not to do a screen print.
> >> >> >> >> > Any ideas?
> >> >> >> >> > Is this information visibile from within VBA? I linked my calendar
> >> >> > to
> >> >> > an
> >> >> > Access database, but did not see a field in the calendar table that
> >> >> > seemed
> >> >> > to
> >> >> > handle meeting attendees.
> >> >> >> >> > --> >> >> > HTH
> >> >> > Dale
> >> >> >> >
> >> >
> >> >> .
> >> >
> >
> >
> >> .
> >>
> .
>