By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,264 Members | 1,277 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,264 IT Pros & Developers. It's quick & easy.

obtaining automation error from Word

P: n/a
I'm learning automation basics here with a Access-Word mail merge.
Specifically I want to obtain a reference to the Word error object....using
Access as an automation client. Is this possible? I've looked over the
Word object model provided in the excellent "access 97 developer's handbook"
and did not find any treatment of this.

I have used Access as a front end to an Oracle database and have been able
to write code to handle ODBC errors vs. the VBA errors from the err object
(they are not always the same). I want to be able to do the same thing with
automation servers.

Anyone doing this and can i see a code sample?

Thanks

--
kent eilers
ke**@kaeServices.com
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
thanks Albert -- but i'm looking for the ability to get to the Word err
object ...not the VBA err object in Access.
"Albert D. Kallal" <ka****@msn.com> wrote in message
news:9A********************@news1.calgary.shaw.ca. ..
Hum, I do have a nice sample database with a working mail merge. The code is designed such that you just have to place one line of code behind a button, and your form is now word merge enabled (it sends just the one record you
are looking at to word). Since the code library works with all forms, then
it means that you don't have to hard code any fields in the merge process.

You might want to read my notes on how I obtained a reliable word merge.
http://www.attcanada.net/~kallal.msn.../msaccess.html
However, I don't have a good word object reference for you.

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.