Your first two questions are not related to Open Access but to Kendo UI. Please post them in the corresponding forums with more detailed information about the problems that you are experiencing and the code that you are currently using. As general information I can say that you can still use OData version 3 with the dataSource by overriding the default schema data
As for your third question - by default OpenAccess ORM maps the Time SQL type to the DateTime CLR type (Date is a shortcut to DateTime in VB.NET). The reason for that is that the Time SQL type can be interpreted as a single point in time while the TimeSpan type represents the difference between two points in time. This behavior is normal and should not be a cause for concern.
Unfortunately we were not able to reproduce the problem you described. In the sample I sent you in your product feedback ticket with id 736177, the retrieved SmokingHour value is the same as the one stored on the server. Could you please confirm if there is difference between the timezones on the server side and application side? Also please check if you have enabled Use UTC for DateTime
in your model settings.
We are looking forward to your feedback.
OpenAccess ORM Q3 2013 Beta is available for immediate download in your account. Get it now
and play with the latest bits. See what's new >>