Naming objects at runtime.

I didn't do anything, except bitch at Chornbe. :D

Thanks guys.

Ok.. I mean agree with you.. I just love your 1st reply. Yeah.. The 1st way is I think the only viable way.

*cracks knuckles* Ok... 1) you simply can NOT maintain that code over time 2) breaks every known rule of OO design in existence 3) objects contain data and the actions you can perform on said data (according to good OO design) 4) the around-the-bend model you would have to create to even come close to making that work is so inefficient as to make your program a resource hog, slow and just way too fragile. 5) I don't even think you could do that in standard code. I think you would have to end up exporting alot of code to .cs files and doing runtime compilation. 6) c'mon... AccountObj.Name is so hard to use?

Yeah.. I love that reply.. "uhm... no, it isn't. You might think it is, but believe me, you don't ".. Why don't you explain to the poor boy, why he doesn't want the 2nd approach. Morgan

uhm... no, it isn't. You might think it is, but believe me, you don't

Actually the second case is the one that I want.

yeah, but you want: AccountObj obj = new AccountObj( "SomeNameFromDB" ) not AccountObj BobsGasStation = new AccountObj(); AccountObj JimsPizzaHouse = new AccountObj(); AccountObj WeBeToyz = new AccountObj(); Right? I hope?

I have a table with account names. I have an “account” class. At runtime I want to create “account” objects (one object for each account in the table) named with the account names.

Kinda vague. You mean you have a table with things like: OleDbCommand or like "Bob"