date comparison #11/05/2017#

Question

I use MyDate >= #11/06/2017# which works on MS Access 2013 32 bits, but I get Reserve error '-' there is no message for this error. The query works take out the date comparison.

Can you please advise what is the way to compare date field in MS Access 2016 64 bits?

Your help and information is great appreciated,

Regards,

Sourises,

Answer 1

That should work in any version of Access. Can you post the entire SQL statement? Maybe something else is causing the error.

---

Bill Mosca
www.thatlldoit.com
http://tech.groups.yahoo.com/group/MS_Access_Professionals

Answer 2

Hi,

And just in case it helps with troubleshooting the problem... What is your current Regional Setting?

Answer 3

US region, M/d/yyyy, I do not change any date time format setting.

It runs well before install MS Access 2016 64 bitd.

I use Windows 7.

Thanks again for helping,

Regards,

Sourises,

Answer 4

 I use Query Builder, but SQL is like following, I use ODBC link to MS SQL Server 2016

The query does not change which worked fine before MS Access 2016 64 bits install.

Select MyTable.MyField from MyTable
where MyTable.MyTime >= #11/06/2017#

Thanks again,

Regards,

Sourises,

Answer 5

Hi sourises,

Same query can run on any version of MS Access.

no any specific change is needed.

I try to test the query with some dummy data and it works correct on my side.

SELECT * from demo_data where version_date>=#10/1/2017#;

Output:

If possible then try to post the screenshot of your data in table and post your actual query if this is not the actual query and you had post the sample query.

further , I search regarding same kind of issue.

I got link below , in which other member had same kind of error in past.

they think that ODBC Driver can cause this kind of issue.

Reserve error -2007

I suggest you to check that you are using a correct driver. if it is not a compatible driver then try to update with correct version of ODBC Driver can solve your issue.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 6

Thanks for the message and helping,

Do I need to use 64 bits ODBC to connect MS SQL 2016?

I use SQL Server ODBC to connect SQL Server tables,

Should I change to SQL Server Native Client 11.0?

Thanks again for helping,

Regards,

Sourises,

Answer 7

Hi sourises,

first try to install the Access Database Engine 2010 (64-bit version!) and check whether the issue get solved or not.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 8

Thanks for the message and helping,

Do I need to use 64 bits ODBC to connect MS SQL 2016?

I use SQL Server ODBC to connect SQL Server tables,

Should I change to SQL Server Native Client 11.0?

Thanks again for helping,

Regards,

Sourises,

I use SQL Native Client 11.0 for all my connections to SQL Server back ends whether they are 32-bit or 64-bit. I'm running Windows 7 64-bit with Access 2010 32-bit but Access 64-bit should also work. Have you tried creating a new DSN?

---

Bill Mosca
www.thatlldoit.com
http://tech.groups.yahoo.com/group/MS_Access_Professionals

Answer 9

Hi sourises,

>> I use Query Builder, but SQL is like following, I use ODBC link to MS SQL Server 2016

Could you share us a screen shot about the linked table records?

To check whether it is related with SQL linked table, if you create a new table like Deepak in Access 2016, will the query work or not?

In addition, for this error message, I suggest you to upgrade Access to 16.0.8424.1000.

# “Reserved error (-7713)” in Access using linked ODBC tables

https://blogs.technet.microsoft.com/the_microsoft_access_support_team_blog/2017/08/11/reserved-error-7713-in-access-using-linked-odbc-tables/

Best Regards,

Tao Zhou

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 10

US region, M/d/yyyy, I do not change any date time format setting.

It runs well before install MS Access 2016 64 bitd.

I use Windows 7.

Thanks again for helping,

Regards,

Sourises,

Could it be that you have the option to use ANSI SQL turned on? If so, you have to use T-SQL language which would be single quotes instead of #.

MyDate >= '11/06/2017'

---

Bill Mosca
www.thatlldoit.com
http://tech.groups.yahoo.com/group/MS_Access_Professionals

Answer 11

Hi sourises,

is your issue solved?

I find that , you did not follow up this thread from long time.

if your issue is solved, then I suggest you to post your solution and mark it as an answer.

if your issue is still exist then I suggest you to refer the suggestions given by the community members.

if then also you have any further issue/ questions then let us know about that.

we will try to provide further suggestions to solve the issue.

I suggest you to update the status of this thread, this thread is still open and will remain open, until your issue get solved.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 12

Thanks all your replies,

I found the issue is that I have some code is not 2016 64 bits Access compatible, it seems that MS Access compiled it first and to check date time, once I fixed the code to be 2016 64 bits compatible then the date format works,

Thanks a million again for replies and helps,

Regards,

Sourises