[AccessD] A2K: <Application Title> can't run the macro or calback function '<FunctionName>'

Mike,

Adding equal sign in front of function name and round brackets after it
doesn't help.
Without wrapper module it still gives:

"The expression you entered has a function name that Microsoft Access can't
find"

for SOME of the calls.

What is weird is that some of them work and some don't work - but they all
work with a wrapper module in FE.

Shamil

----- Original Message -----
From: "Michael R Mattys" <michael.mattys at adelphia.net>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, February 11, 2003 10:05 PM
Subject: Re: [AccessD] A2K: <Application Title> can't run the macro or
calback function '<FunctionName>'


> Shamil,
>
> This error is A2K #7963 from AppLoadString (therefore undocumented)
> If it's really important, I'll investigate further.
> However, the only time I've ever gotten that message was when
> I didn't put "( )" at the end of the function: =myfunction()
> I don't think you can use a Public Sub.
>
> Mike Mattys
>
> ----- Original Message -----
> From: "Shamil Salakhetdinov" <shamil at smsconsulting.spb.ru>
> To: "AccessD" <AccessD at databaseadvisors.com>
> Sent: Tuesday, February 11, 2003 9:02 AM
> Subject: [AccessD] A2K: <Application Title> can't run the macro or calback
> function '<FunctionName>'
>
>
> > Hi All,
> >
> > Here is a tough problem I can't find explanation of:
> >
> > I'm getting (sometimes) the following error message:
> >
> > A2K: <Application Title> can't run the macro or calback function
> > '<FunctionName>
> > Make sure the macro or function exists and takes the correct parameters.
> >
> > <FunctionName> DOES exist but it's located in library database and it's
> > called from TOOLBAR button - i.e. its name is in the OnAction property
of
> > toolbar button.
> >
> > I wrote above that I'm getting this error message SOMETIMES because it
> > appears for some FE program databases and doesn't appear for others but
if
> > it appears once for an FE program database it persists to appear.
> > I know workaround - creating wrapper module in FE database but this
isn't
> > always desirable.
> >
> > I've got this problem first quite a while ago - somewhere in 1998(?)
and
> it
> > was in Access97 when I installed some new software from MS (Office97
> > R1?)  - I can't remember which - before that I used calls from toolbar
to
> > library databases' functions without any problems...
> >
> > Have anybody seen any explanations/descriptions of why this problem
> appears
> > and how to fix it without wrapper modules?
> >
> > TIA for any info,
> > Shamil
> >
> > --
> > e-mail: shamil at smsconsulting.spb.ru
> > Web: http://www.smsconsulting.spb.ru/shamil_s
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com