Docmd.OpenReport CRASHES Access '97

[Jonathan Goldman]

Hi-
I have a relatively simple report that I open in an Access '97 VBA
procedure, using the

Docmd.OpenReport "rptName", acViewNormal

syntax. The problem is that doing this usually crashes Access! No
error message is given, the thing just vanishes! Why? How do I fix
this?

TIA...

[Hans-Joerg Karpenstein]

Am Thu, 15 Apr 2004 09:59:39 -0700 schrieb Jonathan Goldman:

Hi-
I have a relatively simple report that I open in an Access '97 VBA
procedure, using the

Docmd.OpenReport "rptName", acViewNormal

syntax. The problem is that doing this usually crashes Access! No
error message is given, the thing just vanishes! Why? How do I fix
this?

TIA...

Hi,

does the report open when you doubleclick it in the Database
windows?
If this error comes up try to repair and compact the Database
even open it in design-view and save it with another name.
Maybe use another Resolution for the Graphics-driver.
HTH
Karpi
<fluctuat nec mergitur>

[MGFoster]

Jonathan Goldman wrote:

Hi-
I have a relatively simple report that I open in an Access '97 VBA
procedure, using the

Docmd.OpenReport "rptName", acViewNormal

syntax. The problem is that doing this usually crashes Access! No
error message is given, the thing just vanishes! Why? How do I fix
this?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The report object is probably corrupted. One way to fix corrupted
forms/reports is to:

1. Make a copy of the suspected report.
2. Run the new copy.

If the crash occurs again try this:

1. Create a new blank report.
2. Open the corrupted report in design view.
3. For each section on the corrputed report create the same section on
the new report.
4. Copy the corrupted report's RecordSource to the new report.
5. Copy the corrupted report's VBA to the new report's VBA.
6. Recreate the Group/Sorting on the new report, the same as the
corrupted report.
7. Save the new report.
8. Close the corrupted report.

Compile & compact the database. Try running the new report.

If an error occurs create a new Access project/database file & copy all
the objects from the old file to the new one. Compile & compact. Try
running the suspected report.

If failure - start at the report's basics: Does the query run correctly
by itself? Does the query & a new minimumly designed report run
correctly? Etc., until you get to a complete working rpt.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQH7nPYechKqOuFEgEQK+mACgx12JWuD8roNCwn0aYIFOh6 Sa8ssAnicY
b+7ap2UntZwZNbx4JRpN+NXa
=9/aS
-----END PGP SIGNATURE-----