#Error field in report, but only on some machines

[RYankowitz]

Hi all,

A few clients of mine have begun to have trouble with reports. Some of the calculated fields show the #Error value.

What's important here is they only see this on some of their machines. Other machines still operated correctly. Copying the Access .mdb files from the good to the bad machines does no good. They are using Office (and Access) 2003.

A system restore on one of the machines made the problem go away, temporarily.

A complete wipe of the machine, re-installation of Windows XP and Office did not cure the problem.

Suspicion now rests on Office Update.

Has anyone heard of such a problem?

(Unfortunately, all Internet search engines filter out the "#" sign from their searches, so I have not been able to search on "#Error" and find any useful information. That includes Tek-Tips, so if this has been addressed previously, I apologize.)

Thanks,

Bob

 

[dhookom]

When something works on one machine and not another, I always check the references first. Read

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

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]