Little problem with Lebans Print to PDF facility

R

Rli

Hi all,
I am using Lebans facility to print a snapshot to PDF (it works like a charm
on my computer, thanks very much to Stephen Lebans...).
But now a few of my users complain that they get the message

"Sorry...cannot find the DynaPDF.dll file"
even while they are SURE to have this file in the current directory AND in
the windows/system32 directory.

Does anyone have a clou what might cause this?

Thanks for help...
 
R

Rli

Hi Stephen, (nice to talk to you, and thanks for your super work...)
Yes, i still do not understand either....
But i now found out that those same users are having other problems also
(trying to use a vba routine to browse the file system for instance that does
not work on their machine), so the problem is probably not in your soft (so
excuse me for thinking such a stupid thing :)


But anyhow, i downloaded your new print to PDF (version 22 march) and on
testing it on my computer (where the older version did work super) ; it gives
me "Bad DLL calling convention" on the 'how to use' form.

Does that ring a bell?

thanks again,
 
R

Rli

Sorry Stephen,
The "Bad DLL calling convention" error was mine...
I forgot to copy the new dynaPDF.dll and StrStorage.dll to my
windows\system32 (where the old versions where still were present).
Maybe you could first look in the current front end directory and then in
the windows\system32 dir for those files; that would prevent stupid errors
like mine...??
 
R

Rli

Hi Stephen,
Thanks for your explaination...it was stupid of me not to read carefully
your instructions. In my previous post (that did nor arrive i think) i
suggested you first look for those files in the front end directory and then
when not found in windows\system32.

I have however still a problem with the 22 march release.....
The way i proceded to implement your new release is:
I deleted the old modules from my application and created 2 new modules.
Then i copied the integral text of your clsCommonDialog module into my new
one and named it as you did : clsCommonDialog. I did the same for the
ModReportToPDF module.
It works fine now, but....
I had to translate some texts into french and then i tried to compile it.
error: on the lines ......Set clsDialog = New clsCommonDialog
error: Compile error: "A module is not a valid type"

Yet another stupid error of me? Cannot find ou why, recompiling your
original modules does not give that error. ?!?
 
D

Douglas J. Steele

clsCommonDialog is a Class Module, not a regular module. When you're in the
VB Editor, you need to insert a Class Module, not a Module (you cannot do
this by selecting "New Module" from the database window)
 
Top