One customer gets #error

[Bill]

I've got an Access 2002 application that several clients are using.
One of them get the #error in a report column that divides the price
of an apartment by the square footage to show the price per square
foot. The #error is in every row in the report, not just one or two
records.

It's not a data problem, because I had them send me their data file
and I can't duplicate the problem (and neither can they when using a
different PC). The client doesn't have any other problems with the
application.

I don't think there's anything wrong with the report itself because no
other clients get the #error.

So, what's left to check out? It might be an outdated .DLL or
something, but how do I figure it out?

Thanks,
Bill

[Wayne Morgan]

When it's a single computer, it limits the possibilities. Check the
following link for information about references. Also, compare the
references on this computer with one that does work.

http://members.rogers.com/douglas.j....nceErrors.html

Another possible problem would be if the user doesn't have permissions for
the table that the data is coming from for the equation.

--
Wayne Morgan
MS Access MVP
"Bill" <ma*********@yahoo.com> wrote in message
news:51*************************@posting.google.co m...

I've got an Access 2002 application that several clients are using.
One of them get the #error in a report column that divides the price
of an apartment by the square footage to show the price per square
foot. The #error is in every row in the report, not just one or two
records.

It's not a data problem, because I had them send me their data file
and I can't duplicate the problem (and neither can they when using a
different PC). The client doesn't have any other problems with the
application.

I don't think there's anything wrong with the report itself because no
other clients get the #error.

So, what's left to check out? It might be an outdated .DLL or
something, but how do I figure it out?

Thanks,
Bill

[Tym]

On Thu, 18 Dec 2003 03:34:31 GMT, "Wayne Morgan"
<co***************************@hotmail.com> wrote:

Another possible problem would be if the user doesn't have permissions for
the table that the data is coming from for the equation.

I don't think there's anything wrong with the report itself because no
other clients get the #error.
So, what's left to check out? It might be an outdated .DLL or
something, but how do I figure it out?

I know this may sound stupid. But I think it's worth looking *beyond*
the Db to the system, itself. viz: One person I know was having
extreme problems on one PC with a powerpoint presentation. It kept
causing errors, where no other machine did. Turned out to be that this
one PC had hundreds and hundreds of fonts installed, and it was *this*
wich caused Poerpoint to crash.

Now, I'm not saying that this *is* the case here, just that I think
obscure single PC problems may *not* be related to your code at all,
but something else within that PC's system...