Error message

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

When running a query based on a date range, I get an
message "Over flow" and it stops running. the same
message appears when I try to go into the design mode of
the query. I cannot fin what "overflow" means. I can
runf this qury with a 1/1/02-12/31/02 date range just
fine. If I usea shorter, more rcent date range, the error
occurs. What does the message mean?

Thank you
 
The Query is as follows:

SELECT Expr2, Part_ID, WO_Costs, Iss_Qty,
Mat_Cst,SumOfDESIRED_QTY, SumOfRECEIVED_QTY1, Qty_pc,Mat_UC
FROM Query10m

UNION SELECT Expr2, Part_ID, WO_Costs, Iss_Qty, Mat_Cst,
DESIRED_QTY, SumOfRECEIVED_QTY, Qty_pc,Mat_UC
FROM Query13 ;

This comprises th full data in Qury 10m and Query 13.
Query 13 returns 277 records based on November 2003
activity. Query 10m returns 1604 records and is based on
history (Oct 02 - Sep 03). If I run Query 10m for the
period 1/1/02-12/31/02 it runs fine. Anything else and it
dies with the "overflow" message

Thank you
Jeff
 
The Query is as follows:

SELECT Expr2, Part_ID, WO_Costs, Iss_Qty,
Mat_Cst,SumOfDESIRED_QTY, SumOfRECEIVED_QTY1, Qty_pc,Mat_UC
FROM Query10m

UNION SELECT Expr2, Part_ID, WO_Costs, Iss_Qty, Mat_Cst,
DESIRED_QTY, SumOfRECEIVED_QTY, Qty_pc,Mat_UC
FROM Query13 ;

This comprises th full data in Qury 10m and Query 13.
Query 13 returns 277 records based on November 2003
activity. Query 10m returns 1604 records and is based on
history (Oct 02 - Sep 03). If I run Query 10m for the
period 1/1/02-12/31/02 it runs fine. Anything else and it
dies with the "overflow" message

Odd. Can you run query 10m on its own? Could you post its SQL? It
sounds like somehow a date is being interpreted as a division
operation.
 
Yes, I can run both Query 10m and 13 individually without
any difficulty.

That's TRULY bizarre. Sounds like some sort of query corruption to me!

I'd suggest deleting the Union query, compacting the database, and
creating the UNION query again from scratch. If that doesn't work,
maybe try the old trick of creating a new database, importing
everything *except* the UNION query, and building the UNION again, to
get a clean set of systems tables.
 
Back
Top