>I hear (and read) a lot about ORM and I kinda get it, but at a recent .NET user group of about 12 geeks like myself, I asked who used ORM in their development, and NO ONE raised their hand.
>
>So I am coming to .NET from Visual Foxpro based on native free tables, and I am wondering if my work merits starting out with an ORM suite; or should I just use basic ADO to pull down and push back data.
>
>Maybe ORM is only for the really big boys? Who can advise me on this? I write a LOB CRUD app for managing work orders, purchase orders, quotes, time tracking etc. All the data is pretty well normalized and involves around 30-40 tables.

Unless I don't understand what you mean by ORM (Which is possible.)

With Visual Studio Object Relation Mapping seems pretty built in to me. Just add a class based on DataSet or Linq to SQL.