Visio doesn't like bigint identity columns - is it just me?

C

chrisb

(Using Enterprise Architect & sql server 2000)

Test case:
Create a new database model. Add an a table with a bigint identity
column.
Database > Generate (to generate the database).

Check the database - there is a table with a bigint identity column.

Database > Update (to sync the database and the model).
Visio thinks that the database has been changed - it thinks that the
bigint column is now an int column in the database and offers to update
the database. However, the bigint column is still a bigint column in
the database.

No matter how many times do you run Database>Update, visio always
thinks the bigint column in the database has been changed on the
database to an int.

Has anyone else noticed this? Is it just me? Has anyone got a fix for
this?

Thanks
Chris.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Create Table DML from raw Visio XML for database model diagram 1
Visio 2003 Database problems with bigint identity 2
sqlite-odbc write conflict 2
Data type Bigint 1
2007 ADP doesn't recognize BIGINT data type 11
Trying to create a report that will list unmatched records by Ticket Primary Key 0
Why is Aaron 'back'? 12
where did bigint go? 1

Top