D
drew..
This is one of those simple issues that I have always corrected myself,
but am just tired of it. Creating entities in Visio for SQL Server db,
for example a bit field, setting it as required, default to 0. Visio
ignores the default, claiming there is none, adds it own, namely 1, then
proceeds to set the dmo sql to update with an incorrect statement,
causing all kinds of headaches.
Is there a simply work-around or tip anyone knows? thanks kindly, drew..
but am just tired of it. Creating entities in Visio for SQL Server db,
for example a bit field, setting it as required, default to 0. Visio
ignores the default, claiming there is none, adds it own, namely 1, then
proceeds to set the dmo sql to update with an incorrect statement,
causing all kinds of headaches.
Is there a simply work-around or tip anyone knows? thanks kindly, drew..