Sub or function not defined

  • Thread starter Thread starter gkoliver
  • Start date Start date
G

gkoliver

I'm getting a "sub or function not defined" error when I try to run
any procedure in Outlook. My VBA ran fine this morning, then outlook
had some issue (wasn't connecting to the network right, I had to
restart my computer), now it's not recognizing any procedure. I wrote
a simple proc:

Public Sub TestIt()

MsgBox "Hi"

End Sub

When calling TestIt from the immediate window, I get "sub or
function...". When I press F5 in the proc, it works fine.

Is it a security setting issue? Did the hiccup cause a security
setting change?
 
I'm getting a "suborfunctionnotdefined" error when I try to run
any procedure in Outlook. My VBA ran fine this morning, then outlook
had some issue (wasn't connecting to the network right, I had to
restart my computer), now it'snotrecognizing any procedure. I wrote
a simple proc:

PublicSubTestIt()

MsgBox "Hi"

EndSub

When calling TestIt from the immediate window, I get "suborfunction...". When I press F5 in the proc, it works fine.

Is it a security setting issue? Did the hiccup cause a security
setting change?
Click to expand...

And forgot to mention: I've restarted Outlook several times, checked
the security settings, compiled, and restarted the computer twice. No
love.
 
And forgot to mention: I've restarted Outlook several times, checked
the security settings, compiled, and restarted the computer twice. No
love.- Hide quoted text -

- Show quoted text -
Click to expand...

Ok, I finally gave up. I don't know if someone, somewhere changed
something (like a group security policy) and it just didn't show up
until I had to restart Outlook, or if Outlook got wiggy on me, or what
was going on. All my troubleshooting led me to dead ends, despite
hours of Google research. But my travails led me to
EverythingAccess.com, where they have a product that you can download
to use low level MAPI (or something like that), but it circumvents
that dialog box without having to use any Outlook code. No more having
to ensure all my users have the Outlook code installed! YAY! And it's
fast to set up, too... you don't need to have your users do anything!
Not install a DLL, not set up Outlook, etc.

I rarely pay for Access products, but this is one that I paid for
thirty minutes after downloading the trial. Two big selling points for
me: the trial wasn't crippleware, so I was actually able to make sure
it was going to work for me, and I now have a standalone way to send
email via Access... no Outlook setup or DLL installation on client
machines.

My hat is off to the developer... I can only hope to be this good
someday!

gko
 
Back
Top