Office - Handling Access events in .net

Asked By Jak

10-Jun-08 04:34 PM

I asked this in the Access forum and got no responce so I decided to ask here:

I am running an access application inside of a .Net wrapper program using an
Access.Application object.

In this context is it posible to handle Access events (such as the "Click"
event of a command button) with code in the host application?

11-Jun-08 04:27 AM

Hi Jake,

Where would this "command button" be located?

If we're talking about toolbars, then yes; buttons on forms, probably not.
Controls on Forms in Office are strongly linked to VBA modules.

I admit to being somewhat puzzled as to why you'd embed Access when you could
create the interfaces "simply enough" in your .NET form. Excel, Word... Yes. But
a database?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

11-Jun-08 10:49 AM

Cindy,

I could do most of what I am after using toolbars. How would I go about that?

Jacob

11-Jun-08 12:24 PM

Hi =?Utf-8?B?SmFrZQ==?=,

This KB article describes how to create CommandBars in an Office application
and link them to an event handler using VB.NET:
http://support.microsoft.com/kb/303017/en-us
using C#
http://support.microsoft.com/kb/303018/en-us

I have no idea what the differences would be doing this for an embedded
application object, but as long as you've got the application object and the
correct references I'm guessing it shouldn't be a problem.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

11-Jun-08 02:22 PM

THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

Cindy,

This is wonderfull. You've no idea how much you have made my life easyer
over the next year or two.

puzzled as to why you'd embed Access when you could create the interfaces
'simply enough' in your .NET form. Excel, Word... Yes. But a database?"

I am working with a large and complex application that was writen before
my arival on the scene. It is currently writen in Access but I want to
transition to using VB without spending 6 months writing the client from
scratch (which my boss would never let me take the time to do anyway). Being
able to trigger VB code from within Access means that I can transition the
application slowly from Access to VB until everything is in VB and I can
eliminate the Access file entierly.

Thank you again.

Jacob