tag:blogger.com,1999:blog-7756215335050530641.post7062623370864380037..comments2024-03-16T13:59:12.121-04:00Comments on Stacy DuBois' Tech Blog: Access: SQL Server 2008 Date/Time Data Type CompatibilityUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7756215335050530641.post-70128369896154393002014-07-13T14:14:53.727-04:002014-07-13T14:14:53.727-04:00And I've made the same test now with Access 20...And I've made the same test now with Access 2010 (trying to set datetimeoffset(2) to Now() in a form's before update) and it fails in exactly the same manner.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7756215335050530641.post-4862718153133018042014-07-13T13:56:22.981-04:002014-07-13T13:56:22.981-04:00I have the sql server native client 10.0 installed...I have the sql server native client 10.0 installed and still can't update a datetimeoffset(2) in an access 2003 form with a value like Now(). Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7756215335050530641.post-22656451166885765272012-09-29T13:13:52.855-04:002012-09-29T13:13:52.855-04:00Wonderful, thank you for the tip!Wonderful, thank you for the tip!Stacyhttps://www.blogger.com/profile/12016979823644053122noreply@blogger.comtag:blogger.com,1999:blog-7756215335050530641.post-65548490818828159242012-08-12T06:18:00.767-04:002012-08-12T06:18:00.767-04:00Hi Stacy! I`ve been fighting with this problem too...Hi Stacy! I`ve been fighting with this problem too, and the solution that i found was to install the microsoft sql server native client 10.0. You can take it for free from microsoft download center.Hope this will help you. Bye!Albertohttps://www.blogger.com/profile/18144336522323430235noreply@blogger.comtag:blogger.com,1999:blog-7756215335050530641.post-57188993331089192962012-08-07T16:33:28.867-04:002012-08-07T16:33:28.867-04:00Hi Stacy, i found this problem too in my job. This...Hi Stacy, i found this problem too in my job. This week i started to make some test with linked tables from sql server to access 2010, and now i`m a bit dissapointing with microsoft. We are migrating all our datawarehouse from oracle to sql server (2tb and hundreds of date types), and i don`t now why microsoft doesn`t fix this bug in their own products.i`m searching for an updated odbc driver but i think that it doesn`t exist yet. Have you found anything else about this problem? Thank you and sorry for my bad english.Albertohttps://www.blogger.com/profile/18144336522323430235noreply@blogger.com