Re: Type mismatch in a criteria that used to work
- From: John Spencer <spencer@xxxxxxxxxx>
- Date: Tue, 22 Jul 2008 20:17:46 -0400
I have seen that behavior in the past. Query seems to run fine UNTIL you apply criterion, but when you do, it blows up.
Since applying the criteria against the calculated value means that every record is touched and one record with an error seems to be all you need to "blow" the query out of the water.
'====================================================
John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County
'====================================================
Bob Barrows [MVP] wrote:
John Spencer wrote:.SELECT [downtime 1].Date
, [downtime 1].DESCRIPTION
, Left([description],6) AS linetype
, [downtime 1].[reason code]
, [downtime 1].comments
, [downtime 1].duration
, [downtime 1].dtstart
, [downtime 1].dtfinish
, [downtime 1].dtevent
, [downtime 1].[start time]
, [downtime 1].[finish time]
, [downtime 1].shift
FROM [downtime 1]
WHERE [downtime 1].shift=[Forms]![Downtime Report]![Combo58] OR
[Forms]![Downtime Report]![Combo58] is Null
I suspect that the error is occuring in the DownTime 1 query.
That was my first thought, except he said the query runs fine without
the criterion.
- References:
- RE: Type mismatch in a criteria that used to work
- From: RobD
- Re: Type mismatch in a criteria that used to work
- From: John Spencer
- Re: Type mismatch in a criteria that used to work
- From: Bob Barrows [MVP]
- RE: Type mismatch in a criteria that used to work
- Prev by Date: Changing text field to Date
- Next by Date: hh:mm to seconds from midnight
- Previous by thread: Re: Type mismatch in a criteria that used to work
- Next by thread: Re: Type mismatch in a criteria that used to work
- Index(es):
Relevant Pages
|