Runtime all Reports Crash

[KLewisBPM]

I set up a test environment where I had an XP machine without office software. I installed the Access 2000 runtime installation and copied an access database onto it.

The database runs fine all the tables, macros, querys and forms all work fine however when I run any report Access just crashes.

Any ideas would be greatly appreciated.

Kind Regards

Kelley Lewis

 

[SgtJarrow]

First thing I would check is printers....Does this test machine have any printers installed??? Access reports need at least on printer installed on the machine to work properly.

Using the runtime is tough...with no error messages, chasing errors such as these can be tough. I would also confirm that the reports work fine in a full Access install. If they do, the best option is to install full Access on the machine in question, use that to run the application and find out what the error is, then remove Access when done.

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB/Access Programmer

 

[KLewisBPM]

Thanks for the response, my initial thought was an error on the test PC, i installed the runtime in tandem with full office on my PC I used to develop the database and opened it with the same results. Just seems odd that it only crashes out when running a report?

Kind Regards

Kelley Lewis

 

[markphsd]

Installing the runtime probably won't make a difference.

Posting the error if it shows one would. Sometimes there's a Access C+ violation, or sometimes it' just blanks out.

Access crashes if the report is formated improperly for the printer that is avaible.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[Crowley16]

certain printer drivers will also make access reports crash...

--------------------
Procrastinate Now!

 

[markphsd]

What driver's would those be, do you have a list? that's interesting...

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[PHV]

Some HP LaserJet PCL drivers are known to exhibit this.
A workaround is to use a PostScript driver instead.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[KLewisBPM]

Is the drivers of the machine the reports were created with ie formated? I have tried the database using the runtime on 2 different machines using different printers? thanks for your help on this

Kind Regards

Kelley Lewis

 

[KLewisBPM]

Hi all,

I am revisiting this as I have still not found a resolution. I only had 5 reports in the database.

This is what I did... I deleted all of the reports and changed my default printer from UTAX CD1030 to Xerox 7400N I then ran the report wizard creating a very simple report, I checked to ensure that the page setup showed default printer. I linked it in to the switchboard and created a button on a form. and tested it the report ran ok.

I opened the database in Access 2000 runtime, I navigated through the switchboard to the report and ran it the application just crashed. I tried various scenario's and really am at a loss, every aspect of the database works but reports, I have tried setting my default printer to an HP 4000 also. I tried the runtime and database on 2 other PCs both with different printers. I think I have completely exhausted the printer theory.

Can any one think of anything else worth trying?

KLewisBPM