Before I put something together, you should know that I'll be pushing Domain Driven Design (DDD) because it does data access based on Entities. You can start to read up about DDD:

http://domaindrivendesign.org/
http://www.thinkddd.com/
http://www.infoq.com/minibooks/domain-driven-design-quickly
http://www.thinkddd.com/assets/2/Domain_Driven_Design_-_Step_by_Step.pdf

Also, chapter 1 of Martin Fowler's book "Patterns of Enterprise Applcation Architecture" talks about layering your application and how to choose between the three main types of data accees and applying it to domain logic. IMO, this book is a MUST READ for every dev.

>Thanks Craig. Yes, we've spoken before. I do wish that you could have spoken to our CIO. However, they have decided to go with C# as opposed to Java or VB.NET.
>
>Like I replied to Tim Bryan below I'm the only guy who knows C# (beginner+) and we have 250 VFP applications to convert and I feel that I'm the one who needs to guide and sell the direction of the effort and I feel that I'm getting resistance due to ignorance and not knowing what is out there.
>
>No, it's not about my feelings. I know that EF is the best direction to go. I've used ADO.NET and datasets and it was tedious and was a lot of code. We only have two databases and about 100 tables.
>
>I guess I'm looking for information to show the manager that it is a bad decision. Or I suppose to open his eyes.
>
>A lot of this has to do with how everyone freaked out when they saw LINQ because it was new and foreign to them.