There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Solved
Querying SQL Server 2014 ‘date and ‘datetime’ fields from Access 2013
Posted on 2016-07-19
I have years of experience developing Access application with Access backend DB’s. I am now working on an Access 2013 application with a SQL Server backend.
I am implementing a ‘filter’ form that I have created dozens of times in prior Access apps. There are unbound fields at the top of a continuous form. Whatever the user enters in the unbound fields is used to filter the records shown on the bound part of the continuous form. They look like this:
The filter form is working correctly on numeric and text fields but I am having issues filtering dates.
Using degug.print I verified that the SQL generated from the form is correct. This is the generated SQL:
Select * From dbo_vtblEvents Where [EventDate] >= #1/10/2005# And [EventDate] <= #1/30/2005#
I also verified that there is data in the view within the dates specified.
I get zero records on the screen when the query is used as the recordsource of the form.
In the base table ‘EventDate’ is defined as data type ‘date’
I have the view ‘dbo_vtblEvents’ linked to my Access app. When I bring up the view in the table designer, field ‘EventDate’ shows as data type short text.
Event date also shows on the screen as ‘2005-10-10’ instead of “1/10/2005”.
I’m getting the feeling that querying/filtering and even displaying SQL dates is not as straightforward as filtering Access dates.
Does anyone have insight into querying SQL Server dates form an Access application? How do I get the dates to show on the screen in standard ‘1/10/15’ format rather than ‘2005-01-10’?
Any help would be appreciated.
I am implementing a ‘filter’ form that I have created dozens of times in prior Access apps. There are unbound fields at the top of a continuous form. Whatever the user enters in the unbound fields is used to filter the records shown on the bound part of the continuous form. They look like this:
The filter form is working correctly on numeric and text fields but I am having issues filtering dates.
Using degug.print I verified that the SQL generated from the form is correct. This is the generated SQL:
Select * From dbo_vtblEvents Where [EventDate] >= #1/10/2005# And [EventDate] <= #1/30/2005#
I also verified that there is data in the view within the dates specified.
I get zero records on the screen when the query is used as the recordsource of the form.
In the base table ‘EventDate’ is defined as data type ‘date’
I have the view ‘dbo_vtblEvents’ linked to my Access app. When I bring up the view in the table designer, field ‘EventDate’ shows as data type short text.
Event date also shows on the screen as ‘2005-10-10’ instead of “1/10/2005”.
I’m getting the feeling that querying/filtering and even displaying SQL dates is not as straightforward as filtering Access dates.
Does anyone have insight into querying SQL Server dates form an Access application? How do I get the dates to show on the screen in standard ‘1/10/15’ format rather than ‘2005-01-10’?
Any help would be appreciated.
2 Comments
Active 3 days ago
Access hasn't kept up with SQL Server. It does not recognise the Date datatype in SQL Server as a Date value (nor does it recognise DateTime2).
If you look at your linked tables, you'll see that it treats it as a text datatype (the default for everything it cannot resolve).
Try using
CDate([EventDate]) >= #1/10/2005# to make Access try and treat the value as a date - you may have to watch out for where the day, month, year is in the string).
Kelvin
If you look at your linked tables, you'll see that it treats it as a text datatype (the default for everything it cannot resolve).
Try using
CDate([EventDate]) >= #1/10/2005# to make Access try and treat the value as a date - you may have to watch out for where the day, month, year is in the string).
Kelvin
Active today
Thanks for the heads up. After I posted the question I noticed that the date filters worked OK on the fields defined as date time. Just the 'date' fields were the issue.
Even though EventDate only contains a date and no time, I revised the definition in the base SQL table to datetime. The lookup is working as expected now.
I'll stay away from using the 'date' data type in any of the table defs.
Thanks again.
Even though EventDate only contains a date and no time, I revised the definition in the base SQL table to datetime. The lookup is working as expected now.
I'll stay away from using the 'date' data type in any of the table defs.
Thanks again.
Featured Post
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Usually, rounding is performed by some power of 10 - to thousands, hundreds, tens, or integer - or to one, two, or more decimals. But rounding can also be done to a power of two, say, 16 or 64, or 1/32 or 1/1024, even for extreme values.
This following write-up describes a different way to copy Lotus Notes Calendar to Outlook. Along with this, we will also learn the reason behind this NSF to PST migration. Users can prefer different procedures as per their convenience.
Viewers will learn how the fundamental information of how to create a table.
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers.
Hopes this gives you ideas on visualizing your data in new ways ~
Create a calculated field in a query:
…
Suggested Courses
Course of the Month10 days, 23 hours left to enroll
607 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.