Barbara,
Thanks for the response. Yes, the datein field is a date field - it's in a 2.6 table though - not yet upgraded to Visual 6.0 structure, but it is a date field. I tried using the between() function, get's 94% through the query and error recurs. I think it's at the same point as using it as is. I can run a query like "sele * from bcdata where datein between m.startdate and m.enddate" and that works A-OK for the same date range - but when I join with the other tables - it bombs.

Susan



>Susan,
>I use the "Between()" function in SQL rather than the format you have. It MAY make a difference. Also, are you positive all your dates are truly date type variables/fields?
>
>HTH
>Barbara
>
>>This errors has been hitting me in the following sequel statement:
>> SELECT bcdata.*, employee.lastname, ;
>> employee.firstname, employee.cell, routerd.desc, routerd.esthrs, ;
>> routerd.wcenter ;
>> FROM bcdata, employee, routerd ;
>> WHERE employee.empno = bcdata.empno ;
>> AND STR(routerd.wo,9,2) + STR(routerd.seqno,5,0) = STR(bcdata.wo,9,2) + STR(bcdata.seqno,5,0) ;
>> AND bcdata.datein BETWEEN m.startdate AND m.enddate ;
>> ORDER BY bcdata.datein, bcdata.timein, bcdata.wo, bcdata.seqno ;
>> INTO CURSOR ltalldwo
>>
>>The only variables are the m.startdate and m.enddate. The query does work when the date range is 6/10/1999 through 6/14/1999 but not when the start date is 6/1/1999. Set century is on and set date is American and set strictdate = 1. I know this is supposedly a video error, but I haven't any idea why it would crop up here. I ran dSalvage on all the tables and no errors were reported. I reindexed all tables too. Still reports the error.
>>Anybody have any clues as to what could be wrong?
>>
>>TIA, Susan