> I'm using a form for a from/to date for users. I was using the calendar
> control but I ended up with some bizarre "froms" and "tos". I set the
[quoted text clipped - 17 lines]
> here.
> Any clues as to what's happening?
Sorry, here's the SQL. I'm using "Between" Text Boxes that the user inputs.
SELECT dbo_fShopActivity.ActualFinishTime, dbo_fShopActivity.TransactionNum,
dbo_fShopActivity.Employee_CrewID, dbo_fShopActivity.ShiftSetAssigned,
dbo_fShopActivity.ShiftAssigned, dbo_fShopActivity.DepartmentNum,
dbo_fShopActivity.WorkCenterNum, dbo_fShopActivity.rWindow_I_C_S,
dbo_fShopActivity.TransactionName, dbo_fShopActivity.RecordStatus,
dbo_fShopActivity.ActualStartTime, dbo_fShopActivity.AdjustedStartTime,
dbo_fShopActivity.ActualFinishTime, dbo_fShopActivity.AdjustedFinishTime,
Etc. etc. a whole bunch of other fields
dbo_fShopActivity.SerialNum, dbo_fShopActivity.LotNum,
MIRR_SFBP602UF_IIMEXT.INNLBS, MIRR_SFBP602UF_IIMEXT.UNQTY
FROM dbo_fShopActivity LEFT JOIN MIRR_SFBP602UF_IIMEXT ON
dbo_fShopActivity.ItemNum = MIRR_SFBP602UF_IIMEXT.IPROD
WHERE (((dbo_fShopActivity.ActualFinishTime) Between ([Forms]![Report
Parameters]![Text67]) And ([Forms]![Report Parameters]![Text69])))
ORDER BY dbo_fShopActivity.ActualFinishTime;
> I believe the "short date form" applies to the value displayed, not the
> value stored.
[quoted text clipped - 35 lines]
> > here.
> > Any clues as to what's happening?
Jeff Boyce - 31 Jan 2008 01:27 GMT
Can you rewrite the query and use "hard-coded" date values and have it work
correctly?
Regards
Jeff Boyce
Microsoft Office/Access MVP
> Sorry, here's the SQL. I'm using "Between" Text Boxes that the user
> inputs.
[quoted text clipped - 65 lines]
>> > here.
>> > Any clues as to what's happening?
Lambi000 - 31 Jan 2008 17:34 GMT
Jeff,
What do you mean by "hard-coded"?
> Can you rewrite the query and use "hard-coded" date values and have it work
> correctly?
[quoted text clipped - 73 lines]
> >> > here.
> >> > Any clues as to what's happening?
Jeff Boyce - 31 Jan 2008 19:36 GMT
Instead of using a parameter for the user to input a date, use something
like #1/2/2003# (i.e., "hard-code" the dates ... put actual date values into
the query instead of using the parameters).
Regards
Jeff Boyce
Microsoft Office/Access MVP
> Jeff,
>
[quoted text clipped - 85 lines]
>> >> > here.
>> >> > Any clues as to what's happening?