[AccessD] dll deployment

Here is the order of checking for a reference

Access checks to see if the referenced file name is currently loaded in 
memory.
If not, Access verifies whether the RefLibPaths registry key exists. If 
so, Access looks for a named value with the same name as the reference. 
If there is a match, Access loads the reference from the path that is 
pointed to by the named value.

Access next searches the following locations for the referenced file:
Application Folder (location of Msaccess.exe)
Current Folder that you see if you click Open on the File menu  where 
mdb file located
WinDir where the operating system files are running
System Folder located in the WinDir
the PATH environment list of folders directly accessible by the system.

William Hindman wrote:

>gustav/jim
>
>...so this is the way to go? ...no better alternatives around? ...I'm asking 
>because after many years of avoiding 3rd party controls like the plague I'm 
>now forced to use one ...and if I use one, I may be tempted to use others 
>...on first look, this approach would appear to resolve the version issues 
>...but I was certainly hoping someone had already been down this road.
>
>William Hindman
>
>----- Original Message ----- 
>From: "Jim Dettman" <jimdettman at verizon.net>
>To: "'Access Developers discussion and problem solving'" 
><accessd at databaseadvisors.com>
>Sent: Monday, September 11, 2006 5:11 AM
>Subject: Re: [AccessD] dll deployment
>
>
>  
>
>>Gustav
>>
>><<So much for shared DLLs. Wasn't the option to share a DLL one of the
>>reasons to use these?>>
>>
>> Yes, but Microsoft basically gave up on the shared Dll approach years 
>>ago.
>>The recommendation below has been around for many years; a couple of years
>>before .Net in fact.  I'm thinking this came out around the Access 95/97
>>time frame, but I could be wrong.
>>
>> In any case, this recommendation was Microsoft's first (and only that I'm
>>aware of) that the whole concept of shared Dlls simply didn't work.
>>
>>Jim.
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
>>Sent: Monday, September 11, 2006 4:32 AM
>>To: accessd at databaseadvisors.com
>>Subject: Re: [AccessD] dll deployment
>>
>>Hi William
>>
>>No, but thanks for the tip.
>>I love this paragraph:
>>
>><quote>
>>It is good practice to install application DLLs in the same directory that
>>contains the application, even if you are not using DLL redirection. This
>>ensures that installing the application does not overwrite other copies of
>>the DLL and cause other applications to fail. Also, if you follow this 
>>good
>>practice, other applications do not overwrite your copy of the DLL and 
>>cause
>>your application to fail.
>></quote>
>>
>>So much for shared DLLs. Wasn't the option to share a DLL one of the 
>>reasons
>>to use these?
>>
>>/gustav
>>
>>
>>    
>>
>>>>>wdhindman at dejpolsystems.com 10-09-2006 21:47:53 >>>
>>>>>          
>>>>>
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/bas
>>e/dynamic_link_library_redirection.asp
>>
>>...anyone using such redirection with Access?
>>
>>William Hindman
>>
>>
>>-- 
>>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
>>
>>    
>>
>
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada