Reports Preview problem

J

John Johnson

I have MS Office 2003, running various data bases on Access. Win XP
Pro SP2 running on my desktop and laptop.

I just got the lap top and moved, copy those data bases to it. I use
the report feature to print labels.

One seems to work fine but others, when I try to preview the reports I
can a box wanting me to put in the "trim". If I just put the number
"1" in I get only the first line and the word "error" on the other
lines.

The exact same file opened on my desktop works fine. But the new
machine wouldn't even do it when I try to open the same file through
the network on the desktop.

Any ideas?
 
J

Jeff Conrad

in message:
I have MS Office 2003, running various data bases on Access. Win XP
Pro SP2 running on my desktop and laptop.

I just got the lap top and moved, copy those data bases to it. I use
the report feature to print labels.

One seems to work fine but others, when I try to preview the reports I
can a box wanting me to put in the "trim". If I just put the number
"1" in I get only the first line and the word "error" on the other
lines.

The exact same file opened on my desktop works fine. But the new
machine wouldn't even do it when I try to open the same file through
the network on the desktop.
Click to expand...

It is a References problem. The arch-nemesis of Access is missing references.

To fix the References problem follow these steps:
- Open any module in Design view.
- On the Tools menu, click References.
- At least one Reference should say "Missing". WRITE down the one(s) missing.
- Click to clear the check box for the type library or object library marked as "Missing:."
- Close the References Window box.
- Open the References Window back up. Hopefully, nothing should say Missing this time.
- Now go find that library/project(s) in the list that was missing.
- If more than one were missing, find the others and check them as well.
- Close the References box again.
- Now re-compile again. Debug--Compile.
- Hopefully you should not see any more compile errors.

If you'd like to read more about References, here's more info than you could possibly ever want to
know:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

http://allenbrowne.com.au/ser-38.html

http://www.trigeminal.com/usenet/usenet026.asp

http://www.papwalker.com/dllhell/index-page2.html

http://www.access.qbuilt.com/html/gem_tips1.html#DAOLibRef

References that you must set when you use Microsoft Office Access 2003:
http://support.microsoft.com/?id=825796

ACC2002: References That You Must Set When You Work with Microsoft Access:
http://support.microsoft.com/?id=283115

ACC2000: How Access 2000 Resolves Visual Basic for Applications References
http://support.microsoft.com/?id=248941

ACC2000: How to Resolve Reference Issues in an Access Database
http://support.microsoft.com/?id=310803

List of the references that you must set when you work with Access 2000 or Access 97 database:
http://support.microsoft.com/?id=197110

ACC97: References That You Must Set When You Work with Microsoft Access
http://support.microsoft.com/?id=175484

ACC: VBA Functions Break in Database with Missing References
http://support.microsoft.com/?id=160870
 
J

John Johnson

Thanks.

Using a copy of the database I found a missing reference and deleted
that and the database report worked as they should.
 
J

Jeff Conrad

in message:
Thanks.

Using a copy of the database I found a missing reference and deleted
that and the database report worked as they should.
Click to expand...

Excellent, glad I could help.
 
Top