funny, kids probably don't care. Parents do though :laugh:

you would be amazed how long ago that was, just have been using a different ORM (XPO) for a long time. It gives you full control over your transactions. Also you "know" when objects are loading from DB so you don't do validation code of your setters when re-inflating your objects. :^) I don't want to do any Bill (err Steve)Bashing; MS is doing some great stuff, also with the EntityFramework. But if the effort that went into auto-naming the database had gone to validation & transaction management I would be happier I think :)

For the last couple of nights I have been trying to get Entity Framework 4.x to some work and validations within a transaction that I started. :wtf: I have a lead, so may be to night... :~ But I'm sure that if I had opened a connection, started a transaction, done some SQL, done some stuff, do some more SQL, commit, close & dispose. I would have been finished with work so long ago :mad:, that all my beer would be finished now as well. :sigh:

balsy to include your linked in profile so the master of plans can quickly find you :laugh:

Place the public stuff first. That is where the story of your class starts