error when opening access report in xp (error 2100)

[Juddy58]

hello, im currently trying to finish off a clients XP access database (which is meant to be installed by this weekend). The database was actually created by some one else but it is up to me to fix a few errors that it is getting, before it becomes operational

The errors revolve around the reports, when i try to open them, some take forever while on others the program falls over and i get the following error message
Run-time error '2100': The control or subform control is too large for this location

I have searched everywhere (inc microsoft website) and haven't been able to find a clear solution to this problem i have been told that the reports were working fine on the previous designers computer, however on the network i have had no luck, and there are quite a few reports and they are pretty technical so i dont want to mess with them too much or have to rewrite them.

The whole database is only 3meg when compacted and there are other databases running fine on the same network that are 50meg so i cant understand why it is happening

Any help would be greatly appreciated as this is annoying the hell out of me.
Cheers!

 

[jiqjaq]

The error message is not about the size of the database. It's about the size (dimensions) of the controls on the report.

First, you need to verify in the Report setup that the printer for the report/subreport is still valid. If the report was set to print on a printer to which you are not connected, or if that printer has changed its configuration since the report was last run successfully, you will get very long delays opening the report.

Second, make sure that if you use subreports that the height and width will actually fit in the control on the main report.

If the report has VBA code, run it in debug to see where the error happens. If there's no code, add the empty VBA procedures for the sections so you can debug.

Since the reports ran on the previous system, it's most likely not the design of the report. It could be that the References are missing or no longer valid. Check them to be certain. A clean compile only indicates that the VBA code is most likely not at fault. It doesn't verify the data in the design of the report and its controls.

 

[Juddy58]

Thanks for the advice jigjag, I have been told by the client that the reports were working on another system, so im hoping that he isn't talking sh*t.
I will let you know how i go.
Thanks