Greetings,
I created a query (in Access 2010) that joins several linked tables (to an Oracle database). The query runs in about 20 seconds when I filter with a “hard coded” date (e.g., #12/31/2014#). The Oracle table column I’m filtering on is defined as date/time.
When I attempt to change the hard coded value to a “soft coded” value (e.g., Forms![Form1]![Latest_Extract_Date]), the query runs over 5 minutes. In this case, the form field has the exact same value (12/31/2014).
I’ve encountered similar issues using Access 2000, 2003, etc. This is quite frustrating. Does Access interpret #date value# is a special way? Is there a way to trick Access into the thinking a soft coded date is a hard coded date?
Cheers,
Jeff
I created a query (in Access 2010) that joins several linked tables (to an Oracle database). The query runs in about 20 seconds when I filter with a “hard coded” date (e.g., #12/31/2014#). The Oracle table column I’m filtering on is defined as date/time.
When I attempt to change the hard coded value to a “soft coded” value (e.g., Forms![Form1]![Latest_Extract_Date]), the query runs over 5 minutes. In this case, the form field has the exact same value (12/31/2014).
I’ve encountered similar issues using Access 2000, 2003, etc. This is quite frustrating. Does Access interpret #date value# is a special way? Is there a way to trick Access into the thinking a soft coded date is a hard coded date?
Cheers,
Jeff
