Overflow message

  • Thread starter Thread starter Wanda
  • Start date Start date
W

Wanda

I'm not sure which category this belongs in so I will just
put it here.

I have been working on an Access application with a user
interface for a business so they just have to click to
enter data on forms, or view and print reports. Everything
runs on macros and was working until I loaded the database
on their computer so they could add data. When I went back
to check how it was running, they had been getting an
overflow message when they tried to view one of the
reports and it wouldn't display. Another report, which was
copied from that original report and then the source query
was changed in the properties, runs perfectly. I copied
the database with their data to my computer and still get
the Overflow message. I have tried to recreate the report
and I continue to get the same overflow message. I have an
older version of the database (on my computer) with that
report in it and it runs without getting the overflow
message. Does anyone have any ideas on what could have
happened and how to fix it. I cannot find any online help
about the overflow message.

Thank you so much for any help you can give.
Wanda
 
Wanda:

In my experience (for what it's worth) Overflow messages are usually
triggered by one of two things:

1) trying to assign a field or variable a value that is larger than the
field/value definition (i.e., assigning 300 to something defined as a Byte -
which has an upper limit of 255)

2) Division by zero. There is a separate error message for this (especially
if the error is raised in SQL), but, at least in VBA, I have also seen this
to result in Overflow errors.

So, "new" databases get the report, "old" ones don't. Are they using the
same data? (i.e., is the "new" db allowing zeros or nulls in specific table
fields that the old db didn't?) Have the queries or reports changed?
(especially calculations that use division without division by zero
protection) Are there multiplications or additions going on that would
generate results greater than any defined fields/variables can tolerate?

If the Overflow is in the source query as well as the report, try making a
copy (or two) of the query and then run it repeatedly, deleting fields one
at at time, until the error goes away. That may help narrow the search for
answers.

--
Good luck,

George Nicholson

Remove 'Junk' from return address.
 
Back
Top