From: MLH on
Am using StrStorage.dll & DynaPDF.dll
(Lebans tools) for creating PDF's. At most
sites, there are no glitches. However, I
have a problem at one site.

Just so happens its a site on which I mentioned
in another thread that, in spite of my having installed
a runtime application there, I'm apparently not
operating in a runtime environment, as the database
window will display with the right commands.

The Sorry...cannot find the DynaPDF.dll file message
I keep getting is in spite of the fact that the file
exists both in the system32 directory and the
app dir. Anyone set me straight on this?
From: Stephen Lebans on
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.

--

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


"MLH" <CRCI(a)NorthState.net> wrote in message
news:1fhpl2d3v5ugj4fgvp3tk5gm9dd15i6gms(a)4ax.com...
> Am using StrStorage.dll & DynaPDF.dll
> (Lebans tools) for creating PDF's. At most
> sites, there are no glitches. However, I
> have a problem at one site.
>
> Just so happens its a site on which I mentioned
> in another thread that, in spite of my having installed
> a runtime application there, I'm apparently not
> operating in a runtime environment, as the database
> window will display with the right commands.
>
> The Sorry...cannot find the DynaPDF.dll file message
> I keep getting is in spite of the fact that the file
> exists both in the system32 directory and the
> app dir. Anyone set me straight on this?


From: MLH on
I remember that part. And for all but one of the folks I've
recommended this to, it seems to follow exactly what you
said. But for one guy, he has it in the AppDir and even in
System32 - which, of course, is in the PATH. Still, the error
persists. So I'm thinking there might be something unusual
about his system causing this. Dunno.


On Fri, 17 Nov 2006 12:26:40 GMT, "Stephen Lebans"
<ForEmailGotoMy.WebSite.-WWWdotlebansdot...(a)linvalid.com> wrote:

>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: Tom van Stiphout on
On Fri, 17 Nov 2006 08:35:51 -0500, MLH <CRCI(a)NorthState.net> wrote:

So why don't you enhanve the error message to tell you where it looked
for the DLL, and where the AppDir is?

-Tom.


>I remember that part. And for all but one of the folks I've
>recommended this to, it seems to follow exactly what you
>said. But for one guy, he has it in the AppDir and even in
>System32 - which, of course, is in the PATH. Still, the error
>persists. So I'm thinking there might be something unusual
>about his system causing this. Dunno.
>
>
>On Fri, 17 Nov 2006 12:26:40 GMT, "Stephen Lebans"
><ForEmailGotoMy.WebSite.-WWWdotlebansdot...(a)linvalid.com> wrote:
>
>>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: Tom van Stiphout on
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.