[AccessD] duplicate function names

good idea.
Jim

-----Original Message-----
From: John Skolits [mailto:askolits at ot.com]
Sent: Monday, July 31, 2006 10:41 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] duplicate function names


Jim,

I prefix all my library files with a "lbf_" (library file) prefix. This
makes sure there is no confusion. You should come up with some kind of
prefix of your own for library functions.

John

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Monday, July 31, 2006 7:11 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] duplicate function names

This can be useful.  You might have a 'generic' function in your library,
but with some installations you need to do something a little different.
With the function in the main database taking preference, you don't need to
change the library.

Dan Waters
 
-----Original Message-----
Subject: [AccessD] duplicate function names

Maybe everyone but me knows this, but I just stumbled upon the fact that it
is possible to have two functions with the same name coexist. If one is in a
module in the current database and the other in a module in a referenced
code library Access will use the function in the current database and ignore
the version in the code library. Everything compiles and runs fine at least
in access 2000. Whether or not this is useful or merely dangerous is a
different question.

Jim Hale


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.