The Jet engine knows nothing about VBA. The Access UI ties them together
closely, but as you have found, outside of the Access environment, no VBA
code is visible to Jet. Sorry to be the bringer of bad news.
Jet and Access are separate entitie, so you do not have an
Access query, you have a Jet query.
When you use Jet outside of Access, then Access and your VBA
module are not available.
--
Marsh
MVP [MS Access]
If you need query results that involve a user defined function while in an
external program (say, Excel), you need to open an instance of Access via
Automation, run the query and grab the results.
--
HTH,
George
"nonlinear" <nonl...@discussions.microsoft.com> wrote in message
news:7FFD46F0-CFC9-44AC...@microsoft.com...
--
HTH,
George
"George Nicholson" <Georg...@Junkmsn.com> wrote in message
news:%23TE3U3i...@TK2MSFTNGP04.phx.gbl...
"How you can implement Sandbox mode is extended in Jet 4.0 Service Pack 8 to
be more compatible with Access databases. Previous implementations of
Sandbox mode were too restrictive for most Access applications. Starting
with Jet 4.0 Service Pack 8, the enhanced Sandbox mode continues to block
unsafe Visual Basic for Applications functions, but Jet 4.0 Service Pack 8
now permits the execution of user-defined functions."
"..now permits execution of user-defined functions." isn't a newly
introduced feature, its a Sandbox mode bug fix.
--
HTH,
George
"nonlinear" <nonl...@discussions.microsoft.com> wrote in message
news:0410141B-0540-4F95...@microsoft.com...