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

Application.Run or not as the case may be.

P: n/a
I have created an Access Menu Add-in which manipulates data in a
table. This add-in is saved as a *.mde file and works fine. The
add-in contains a public sub which is to be accessed by another
database. I have used the Application.Run command -
Application.Run("AddinName.SubName", InputVariable) - and this is
where the problem lies.

If I have opened my add-in during the current Access session then
application.run is fine. However if it has not been opened the
reference cannot be made - Runtime Error 2517, Access can't find
procedure AddinName.SubName.

I'm guessing that it is the nature of my addin which is causing the
problem. I am trying to use a menu add-in as if it were a library
add-in. Are there any modifications I can make to the USysRegInfo
table to cater for this scenario. Unfortunately I can't really split
this into two different add-ins because the function is intrinsically
linked to the actions of the menu add-in.

Of course I could be barking up the wrong tree altogether.

I hope this makes sense. Any help would be very gratefully received.

John
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.