[AccessD] Library order matters

Or without re-saving them?

On 16 Sep 2010 at 13:51, jwcolby wrote:

>  > Probably a side effect of queries being "optimized" by JET when you
>  save them.
> 
> Yep.
> 
> Really I just wanted to put it out there that queries referencing
> functions can cause issues that can't be fixed without a decompile.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> On 9/16/2010 1:13 PM, Heenan, Lambert wrote:
> > Probably a side effect of queries being "optimized" by JET when you
> > save them.
> >
> > Lambert
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> > Sent: Thursday, September 16, 2010 12:42 PM To: Access Developers
> > discussion and problem solving Subject: Re: [AccessD] Library order
> > matters
> >
> > In fact it uses direct calls into both.
> >
> > Now comes the fun part...
> >
> > Remember decompile?  Well...
> >
> > I have a query that references Fltr().  Once I change the order of
> > the references, calling fltr in the debug window correctly calls the
> > fltr function in C2DbFW3G.  However the query still calls the fltr()
> > in C2DbLWS.  I had to decompile compile to cause the query to call
> > fltr in C2DbFW3G.
> >
> > Once I changed the order AND decompiled / compiled, the problem I
> > was having went away.
> >
> > This is a problem that could apparently not be fixed without a
> > decompile.
> >
> > John W. Colby
> > www.ColbyConsulting.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>