It's true that it won't work calling it from outside of Access (that's
because when you're calling from outside of Access, you're strictly going
through the Jet Engine, which doesn't know anything about user-defined
functions), but why do you think it won't work calling it from a procedure?
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
"Manuel" <(E-Mail Removed)> wrote in message
news:450801c37689$b75feca0$(E-Mail Removed)...
>
> However, that will only work within a querydef. If you
> want to call it from a Procedure, or from outside Access
> through ODBC, you'll keep getting that ugly error. See
> Q180810 in the Microsoft knowledge database
>
>
> >-----Original Message-----
> >Also, make sure you didn't name the module the same as
> the function.
> >
> >--
> >Doug Steele, Microsoft Access MVP
> >http://I.Am/DougSteele
> >
> >
> >"Chris" <(E-Mail Removed)> wrote in message
> >news:24e501c3733b$79f10850$(E-Mail Removed)...
> >> You don't have to do anything specific. Just make sure
> >> the Function is marked as Public.
> >>
> >> Public Function DateDiffW()
> >>
> >>
> >> Try calling it from the debug window and see if it
> works.
> >>
> >>
> >> Chris
> >>
> >>
> >>
> >> >-----Original Message-----
> >> >I have copied the user defined function DateDiffW(),
> from
> >> >the MS Knowledge base and inserted into a module within
> >> my
> >> >database. When I go to use this function in a query or
> >> >report, I get the message User-defined Function not
> >> >defined.
> >> >
> >> >What are the steps that I need to take in order for a
> >> user
> >> >defined function to be recognized?
> >> >
> >> >Thanks,
> >> >Tim
> >> >
> >> >.
> >> >
> >
> >
> >.
> >