ORM - best practice wanted

I would like to see some best practice guidance on using an ORM in general, illustrated with OpenAccess code(c#/vb), from telerik.

I know it's a matter of coding "taste" - but if you could list ex. 3 samples for asp.net, three for winforms and so on.

The samples could illustrate 1-2-3-n layer coding. Where to place the logic. Where and when to connect to the db.
(with your motto: "Deliver more than expected" - I am sure you will do more).

One of the "dangers" with ORM systems, in my opinion, is that it tend to be very technical and complicated - and only the really
hardcore types will continue to follow the debates on such forums. More will "give up" and turn back to the way they did it "before".

It would really help us to get this area de-mystified with some good and practical guidance from you.

Regards,
Bo Hessner