ReportToPdf (by Stephen Lebans) crashes Access!

[computersciencestudent]

I'm using ReportToPDF to convert a report to PDF (obviously). It exports the
report to a PDF file just fine, but it crashes EVERY TIME. It will just
export the report and crash.

When it crashes, it gives this error message:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience."

I have tried storing the 2 .dll's in the same folder as the .mdb file and in
the System32 folder. I get the same result both ways.

Any ideas???

 

[Stephen Lebans]

There has never been a reported case of ReportToPDF causing an error. Can
you Email me your MDB so I can have a look at it here?
(e-mail address removed)

What version of Access are you using?
What version of Windows?

--

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

 

[duanemoore]

I'm using ReportToPDF to convert a report to PDF (obviously). It exports the
report to a PDF file just fine, but it crashes EVERY TIME. It will just
export the report and crash.

When it crashes, it gives this error message:

"Microsoft OfficeAccess has encountered a problemand needs to close. We
are sorry for the inconvenience."

I have tried storing the 2 .dll's in the same folder as the .mdb file and in
the System32 folder. I get the same result both ways.

Any ideas???

That error message is so sickening! I got an .mdb from a friend that
had a Microsoft internet control on it and only 3 lines of code. It
was supposed to take an address from a table, construct a URL, then
open that page in the internet control on my form. It worked fine for
my friend. It worked fine for me. I included it in my commercial
application and crashed and burned for my client.

There are many references to database corruption on the web. But
sometimes, this message just means that Microsoft Access is full of
bugs that aren't going to be fixed any time soon.

The venerable Outlook 2000 has started to crash with this message.
Follow the Microsoft links, and it essentially asks you to buy the new
version. Could some of those updates introduce errors in stable old
products for the sake of money?

Good luck!