I'm designing a database and when generating the design on SQL 2000 or 2005 the rules are too strict and won't let me generate the database. For instance: 2 tables with columns named "Foo" must have the same datatype. Great idea in theory but... Anyway, I'd like to be able to change the rules but can't figure out how. Any help would be appreciated. -chris (using Visio for Enterprise Architects 2005)
I'm assuming with the lack of response that there is no way to do this. I've been able to work around the problem by changing the "Conceptual" datatype to something different when a conflict occurs and leaving the "Physical" datatype the same. This works OK. -chris "Chris Yager" <chris.yager@gldsolutions.com.invalid> wrote in message news:e4o57SBEGHA.3064@TK2MSFTNGP14.phx.gbl... > I'm designing a database and when generating the design on SQL 2000 or > 2005 the rules are too strict and won't let me generate the database. For > instance: 2 tables with columns named "Foo" must have the same datatype. > Great idea in theory but... > Anyway, I'd like to be able to change the rules but can't figure out how. > Any help would be appreciated. > > -chris > > (using Visio for Enterprise Architects 2005) >
I just wanna learn! If the two columns in the two tables are linked, why would you NOT want them to share the same datatype? I encountered this error when checking my database model and, it helped to highlight errors made by the developer of the database. A good thing.
