[AccessD] Library order matters

A lot of us learnt that lesson  when upgrading from 97 to 2000 (IIRC).

Lots of errors cropping up because the order of references to ADO and DAO  
resulted in people creatinf ADO.Recordsets when the thought they were dealing with 
DAO.Recordsets.

-- 
Stuart  

On 16 Sep 2010 at 12:21, jwcolby wrote:

> 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.
> 
> 
> 
> -- 
> John W. Colby
> www.ColbyConsulting.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>