[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

On 9/16/2010 12:33 PM, Heenan, Lambert wrote:
> If your front end app does not make any direct calls to C2DbLWS, but instead is using routines in C2DbFW3G then it should also work if your app just has a reference to C2DbFW3G and no reference to C2DbLWS at all.
>
> 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:21 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Library order matters
>
> I use libraries.  My C2DbFW3G (framework, 3rd generation) has a function called fltr().
>
> C2DbFW3G references C2DbLWS (my old Light Weight Security framework).  C2DbLWS has a function fltr().
>
> So...
>
> My front end references BOTH C2DbLWS and C2DbFW3G in that order.
>
> C2DbFW3G is setting filters for the application, but when the application calls fltr() to get the resulting values, because it references C2DbLWS first, it calls fltr in C2DbLWS and of course it returns a null value.
>
> Reversing the order of the reference in my application now allows the application to call fltr in C2DbFW3G and that fltr() has the right value.
>
>
>