Prev: Why does fso.MoveFolder fail with "Permission denied"?
Next: campo dependiente de otro en un formulario
From: Stephen Lebans on 17 Nov 2006 11:40
Hi Tom,
two reasons:

1) I would prefer the DLL be placed in the same folder as the front end
MDB/MDE. For XP and later, MS strongly suggest this course of action.

2) The behaviour of which and what order WIndows searches is different
across all of the windows versions.

For the last several months, I have been receiving on average, 3 - 5 EMail
requests a day for help with my ReportToPDF solution. In 90% of the cases,
users do not follow my instructions for locating the DyanPDF DLL.

I'm just trying to reduce Tech support requests.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.


"Tom van Stiphout" <no.spam.tom7744(a)cox.net> wrote in message
news:chjrl2ha898ofq6c0mehv7vfp3dp0tfbb3(a)4ax.com...
> On Fri, 17 Nov 2006 12:26:40 GMT, "Stephen Lebans"
> <ForEmailGotoMy.WebSite.-WWWdotlebansdot...(a)linvalid.com> wrote:
>
> Stephen,
> I haven't seen the code for DynaPDF, but why are you checking if it
> exists, rather than allowing Windows to do what LoadLibrary normally
> does, which includes checking for the DLL in various locations
> (AppDir, CurDir, SystemDir, etc) in a defined order? Some might say:
> so I can control which version is used. But then I say: not if you're
> the second app and another copy of the library is already in memory.
>
> If the OP wants that behaviour, he could just comment out the check
> for existence, and the path part of the filename passed into
> LoadLibrary.
>
> -Tom.
>
>
>>The DLL should reside in the same folder as the Front End of your app. If
>>you look through the code you will see it checks the current folder to see
>>if the DynaPDF DLL exists and if so calls LoadLibrary against it.
>


From: MLH on 18 Nov 2006 08:01
Makes sense to me, your objective. In my case, I have
it in two places ==> didn't really expect that to remedy
the issue. But hey, one never can tell.

Could it be that my runtime installation there is complicated
by the fact that the user also runs retail version of A97 on
his machine? I even tried putting the dll in c:\program files\
Microsoft Office\ there with the msAccess.exe file. Didn't
help me.
First  |  Prev  | 
Pages: 1 2
Prev: Why does fso.MoveFolder fail with "Permission denied"?
Next: campo dependiente de otro en un formulario