I have Visio for Ent Architects SP-2 (10.0.5110) and an SQL-Server (2000 sp3). In a project i need to work with a considerable amount of GUIDs (uniqueidentifiers). The problem is that updating a table (that contain a non-nullable GUID field) that has been changed in visio and thus shall be propagated to the db fails. After examining the DDL-script it appears that things go wrong in the beginning of the update process... The first step is to create the temp table (xx_IM0) - this work all right, and the next step - that is to move the data from the original table to the temp table fails. The minor step between these two step - setting the identity-insert works ok as well. The table that is being edited/updated is empty btw. Thus, - the generated DDL-script is not working. I can manually edit the DDL script and get it to work, - but... Is there a reasonably smooth way to do this? Can I intercept the update cycle? Is there a workaround? BR /J
