[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