Re: dynaPDF.dll and Runtime A2003 = Crash
- From: franc sutherland <franc.sutherland@xxxxxxxxxxxxxx>
- Date: Tue, 20 Oct 2009 01:38:54 -0700 (PDT)
On Aug 26, 5:53 pm, "Tony Toews [MVP]" <tto...@xxxxxxxxxxxxxxx> wrote:
franc sutherland <franc.sutherl...@xxxxxxxxxxxxxx> wrote:
I am using the dynaPDF solution for printing reports to PDF
documents.
On my own machine using the full Access 2003 it works fine.
However, on a client's machine using just A2003 Runtime, it crashes.
The "Microsoft Access has encountered a problem",etc dialog box comes
up.
Is this a problem that other people have come across?
Double check that the VBA code that you're using from Leban's site is the current
code that goes with the latest DLLs. Are both DLLs in the same folder as your FE?
Are you passing the routine a legal path and file name with no special characters? A
client just reported though that the Lebans solution silently fails which causes the
users confusion.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
Granite Fleet Managerhttp://www.granitefleet.com/
Hi Tony,
The two DLL files are in the same folder as the FE. It seemed to be
the File Dialog box which was causing it to trip up. When I put the
file location in the code, it worked OK.
I took your suggestion and copied the most recent DLL files from
Stephan Lebans' site, and this has resolved the problem.
I'm a bit lost as to why it stopped working on the runtime version
although it had been working with the previous DLL files for some
time.
It's all working fine now.
Thanks for your help.
Franc.
.
- Prev by Date: Re: dynaPDF.dll and Runtime A2003 = Crash
- Next by Date: Re: Capturing ODBC errors in Access 2003
- Previous by thread: Re: dynaPDF.dll and Runtime A2003 = Crash
- Index(es):
Relevant Pages
|
