FB Writes >I think you are talking about Halpin's Object Role Modelling templates >in visio for enterprise architects and the others are talking about >Object Relational Mapping. The acronym 'ORM' is more used with Halpin's >method (as you do, which is correct) than with O/R mapping, nevertheless >it can lead to misunderstandings as in this case :D
>If I might add: the ORM (abstract database model modelling method, >halpin/nijssen: http://www.orm.net) tool in visio could be extended to >produce classes/mappings as well if MS is clever, after all, then you'll >have 1 modelling mechanism on an abstract level which would lead to a >solid relational model and would lead to a base for further class >modelling. James Writes: You are absolutely correct in both respects. I did misunderstand the original message do to the Acronym involved. :D Object Role Modeling and Object Relational Mapping could be integrated to create an easy way to produce classes/mappings to DB objects. It is the way I use the Object Role Modeling and UML tools that come with Visual Studio E.A. that made me believe it could be what he was looking for. Automated class generation of Database objects now as opposed to years from now. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
