This question is locked. New answers and comments are not allowed.
Hi all,
Every once in a while (completely at random) I get a datetime overflow when inserting or updating a record that contains one or more datetime fields. (SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999)
When checking the object that's saved by OpenAccess, all present datetime fields are filled and in range. There should be absolutely no reason why it gives me an overflow exception. When I reset and try to insert/update the same records, sometimes it works.
This behaviour seems to happen more often when using the GetContextPerRequest method found in the best practices but also when always initiating a new instance.
Any ideas?
Erik
Every once in a while (completely at random) I get a datetime overflow when inserting or updating a record that contains one or more datetime fields. (SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999)
When checking the object that's saved by OpenAccess, all present datetime fields are filled and in range. There should be absolutely no reason why it gives me an overflow exception. When I reset and try to insert/update the same records, sometimes it works.
This behaviour seems to happen more often when using the GetContextPerRequest method found in the best practices but also when always initiating a new instance.
Any ideas?
Erik