Hello Bill Murphy,
1. Yes, you are looking at the right place, the per-thread context is the best and proven approach with OpenAccess. We also have recommended this approach to our customers in the following blog post. It discusses the management of the IObjectScope but the rules are absolutely the same, it is just a different API.
2. Yes, you answered the question right. The CRUD operations are internally executed inside a transaction.
3. First, I should mention that for the next service pack release which is coming soon, the OpenAccessDataSource will be working with the new visual designer entities and the new OpenAccessContext. Doing the CUD operations in code is usually done by subscribing for the appropriate events of the UI controls, then obtaining the object by its ID and then assigning the required values to it, or deleting it from the context for example. I would suggest you downloading the following code library example which is also part of our QuickStart. There we are using the old API in a disconnected scenario, but I think that it should really be enough for getting your started as the CUD operations are there performed in code and the same approach will work with the new context as well.
4. Yes, the DataServicesWizard does work for creating WCF layer over OpenAccess but it is not yet fully integrated as part of the product. So it is still a separate product that you should download from the Telerik web site and install it on your machine after you have installed OpenAccess.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.