Good Looking Bloke
Registered User.
- Local time
- Tomorrow, 04:58
- Joined
- Oct 15, 2019
- Messages
- 30
I have a real hard time with time...sometimes it works fine. Others, well not so much is a nice explanation for not at all rhyming with duck.
Todays challenge should anyone choose to accept it before I explode is the following:
This SQL is throwing an error something to do with the #5:15:00 AM#...which is really weird as this is fed from the identical query one step before.
The query above is based on qryVisitTime which looks like:
qryA is simply a holding query it doesnt do anything its instead of working on the raw table data...separation of concerns so to speak.
Todays challenge should anyone choose to accept it before I explode is the following:
Code:
SELECT qryVisitTime.TimeCut FROM qryVisitTime WHERE (((qryVisitTime.TimeCut) > #5:15:00 AM# ORDER BY qryVisitTime.TimeCut;This SQL is throwing an error something to do with the #5:15:00 AM#...which is really weird as this is fed from the identical query one step before.
The query above is based on qryVisitTime which looks like:
Code:
SELECT WeekdayName(Weekday([Visit Date])) AS Week_Day, qryA.[Visit Time], qryA.[Member ID], Month([Visit Date]) AS VisitMonth, TimeSerial(Hour([Visit time]),(Minute([Visit time])\15)*15,0) AS TimeCut
FROM qryA;qryA is simply a holding query it doesnt do anything its instead of working on the raw table data...separation of concerns so to speak.
