Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
You are kind of contradicting yourself here Tony, because having libraries in the application directory only works consistently if the application runs from the application directory, which yours (cvsnt.cpl) doesn't. Requiring - as you do - that the application directory is placed as the very first thing in the system path, only works as long as no other applications with the same requirement is installed. You would need to fix that, making your application as well behaved as you require of other applications below. /Jakob "Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message news:digm9s$89v$1 at paris.nodomain.org... > Anthony Williams wrote: > >> If you want an applet to run safely, the best thing is to ensure that it >> runs >> fine, whatever the current directory is, and whatever is on the path, >> which >> either means static linking of dependencies, or modifying the DLL names >> (e.g. cvsnt_iconv.dll, cvsnt_expat.dll) > > This happened because someone put a copy of iconv.dll in system32.. I'd > *expect* breakage in that case (and not just of cvsnt either). > > Libraries used by applications should be in the application directories, > nowhere else. Static linking of cvsnt.cpl is just not practical as it > depends on the rest of the cvsnt system to work - it isn't linked directly > to iconv.. it's linked to cvsapi, cvstools and the various installed > modules (determined at runtime). cvsapi in turn is linked to iconv, the > various databae DLLs (loaded as needed at runtime), etc. > > Tony