A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Running & Setting Up Queries
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

= #Date# problem



 
 
Thread Tools Display Modes
  #1  
Old September 9th, 2008, 01:49 PM posted to microsoft.public.access.queries
darren via AccessMonster.com
external usenet poster
 
Posts: 11
Default = #Date# problem

Putting together a simple query and noticing some abnormal behaviour e.g.

= #31/7/08# is excluding 31/7/08???

Any ideas?

Thanks

--
Darren

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...eries/200809/1

  #2  
Old September 9th, 2008, 02:06 PM posted to microsoft.public.access.queries
John Spencer
external usenet poster
 
Posts: 7,815
Default = #Date# problem

A guess is that the records also have a time component that you are not seeing.

Try #2008-08-01# and see if you get the expected records.

If so, then your records have a time component as part of the date - this
often happens when someone uses the Now() function to assign a date instead of
using the Date() function.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

Darren via AccessMonster.com wrote:
Putting together a simple query and noticing some abnormal behaviour e.g.

= #31/7/08# is excluding 31/7/08???

Any ideas?

Thanks

  #3  
Old September 9th, 2008, 02:20 PM posted to microsoft.public.access.queries
darren via AccessMonster.com
external usenet poster
 
Posts: 11
Default = #Date# problem

Hi John

Just found this as you have replied. Indeed some records have a time
component!

Thanks

John Spencer wrote:
A guess is that the records also have a time component that you are not seeing.

Try #2008-08-01# and see if you get the expected records.

If so, then your records have a time component as part of the date - this
often happens when someone uses the Now() function to assign a date instead of
using the Date() function.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

Putting together a simple query and noticing some abnormal behaviour e.g.

[quoted text clipped - 3 lines]

Thanks


--
Darren

Message posted via http://www.accessmonster.com

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 09:03 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.