|
||||||
Access Bug Alert #Deleted By Richard Rost ![]() ![]() ![]()
This has to do with issues with how SQL Server is handling a new type of datetime value. The easiest solution for now is to simply rollback the update and go back to the previous version. Alternately, Microsoft has posted some fixes on their website that you can try as well.
So far I've only heard from a couple of you that are experiencing this problem. Personally, I haven't encountered it, and I have automatic updates ON and I'm using SQL Server, so it doesn't seem to be affecting everyone. If you're having this problem and need more help, let me know. If enough people are having problems, I'll put together a video or more help on what to do.
|
||||||||||||||||||||||||||
Check out these other pages that may be of interest to you: |
|
| |||