So far, I find Data Access to be a fine ORM, as compared to Entity Framework. The API is less cluttered than even EF's DbContext. It handles object generation across junction tables in the datastore quite well (I'm doing database-first).
I do note some odd behavior when generating an object based on a table which contains a column of type byte array. A warning states, "Explicit change tracking required for the array field...etc.", Line: 16707566, Column: 1
Double clicking on this warning results in an exception, because of the HUGE line number: "The operation could not be completed. The parameter is incorrect."
What is meant by the warning that explicit tracking is required? How do I explicitly track such a field? Then, how do I get rid of the warnings?
I also note that generated classes contain an Import of the model namespace. This seems unnecessary.
Also, your emitted VB is really (really) bad. It looks like C#, which quite defeats the purpose. Y'all are in serious need of the services of a professional VB developer :)
In spite of the problems, I see promise in it - for two main reasons:
1. Telerik Data Access seems to have very good performance.
2. Telerik Data Access targets SQL Server 2000.