Simple Oracle SQL date syntax question

calendar_today Asked Nov 18, 2008
thumb_up 14 upvotes
history Updated April 14, 2026

Direct Answer

In Oracle, your date should be written as an ANSI date literal like this: DATE '2008-11-11' Or converted to a date from a string like this: TO_DATE('11/11/2008', 'MM/DD/YYYY') See…. This is an advisory response with reference links, ranked #18th of 67 by community upvote score, from 2008.


The Problem (Q-score 6, ranked #18th of 67 in the Access VBA archive)

The scenario as originally posted in 2008

I am trying to convert a working MS Access query to run on an Oracle database being accessed via VB Script (.asp). This is the last section of the WHERE clause:

sql = sql & "WHERE (UAT.HB.MB_MODE = 'A' AND   UAT.HB.PRINT_DATE >= '" 
& SD & "' AND UAT.HB.PRINT_DATE <= '" & ED  &"'  )"

The variable “SD” (i.e. “start date”) is a text string that can contain a value such as “11/11/2008”. The same goes for the variable “ED” (i.e. “end date”).

However, the dates do not work. Does Oracle require a special way to use dates?

Do the dates have to be converted? Do I surround them with the ‘#’ keyword like you would in MS Access?

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — strong answer (top 25 %%) (+14)

Advisory answer — community consensus with reference links

Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.

In Oracle, your date should be written as an ANSI date literal like this:

DATE '2008-11-11'

Or converted to a date from a string like this:

TO_DATE('11/11/2008', 'MM/DD/YYYY')

See http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements003.htm#BABGIGCJ


When to Use It — vintage (14+ years old, pre-2013)

Ranked #18th in its category — specialized fit

This pattern sits in the 55% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2008 and 2026

The answer is 18 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Why does this sit in the top quartile of Access VBA answers?
expand_more

Answer score +14 vs the Access VBA archive median ~4; this entry is strong. The score plus 6 supporting upvotes on the question itself (+6) means the asker and 13 subsequent voters all validated the approach.

This answer links out — what are the reference links worth following?
expand_more

Read the first external link for the canonical reference, then search this archive for a top-10 entry in the same category — advisory answers are best paired with a ranked code snippet to close the loop.

This answer is 18 years old. Is it still relevant in 2026?
expand_more

Published 2008, which is 18 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #17?
expand_more

The pattern one rank above is “How do I create a passthrough query in access using a DSN-less connection?”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 14, original post 2008, ranked #18th of 67 in the Access VBA archive. Last regenerated April 14, 2026.

ms-access