Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Evil visio bug, help!

117 views
Skip to first unread message

LP Redmond

unread,
Feb 12, 2002, 12:54:41 PM2/12/02
to
I am using Visio 2000 SR-1.
I am building a database model that consists of 10 pages and 35 tables using
a Microsoft SQL Server Driver.
I have also visited Microsoft support site and viewed this newsgroup
regarding my problem and haven't discovered a solution.
I have stumbled accross what appears to be a bug and I am getting
frustrated. Here is what happens:
I go to "Database|Generate"

and then promptly get an error like this:
(Error 1)
L:\IS\...\DOCS\IMPORTAPP.VSD : error L3001: 'relParameters2ReportLog' :
Parent column(s) not specified.
L:\IS\...\DOCS\IMPORTAPP.VSD : error L3002: 'relParameters2ReportLog' :
Child column(s) not specified.
L:\IS\...\DOCS\IMPORTAPP.VSD : error L3016: 'relParameters2ReportLog' :
Relationship must exist between a primary key or an alternate key
designated as unique constraint.

(Error 2)
I double click on the error line and get another error message:
"This relationship is not shown because the entities it is connected to are
not placed on the diagram"

Scratching my head, I try a troubleshooting technique -- I create insert
another blank page on my document select all my tables and drag them onto
the new page. I now see the relationship that didn't exist before. I
delete the relationship and try the "Database|Generate" again. Once again I
get the first error above; and when clicking on it I get the second error.
I retry my troubleshooting technique by dragging all the tables onto a newly
created page and there is that rogue relationship again. It will not die,
and it will not be killed.

I decide to outsmart the stupid thing by dropping the table that is
referencing that rogue relationship. Now I go to run "Database|Generate"
again and what happens?
The 1st error is gone, however, I now have another relationship that is
exactly like the 1st error, but it is pointing to a new set of tables. Now
an error that didn't used to be there is now there. Visio 2000 appears to
be generating these rogue relationships and I cannot get rid of them. I
have dropped 3 tables from the model hoping to add them later and hoping
that this will fix my problem, but each time the error messages appear with
a different relationship that is missing an parent and child column.

I did one other thing that did work, but I don't like it. I created a brand
new Visio document and copied 1 page of all the existing tables and
relationships from the old document to the new. I then did
"Database|Generate" And to my surprise, it worked with no errors; however,
one big datamodel from 35 tables is very ugly and I now will have to
re-create the 10 pages which will be very time consuming.

Has anyone had this happen before, and is there a better way to fix this
problem? Does Visio have a certain threshold of tables that if passed will
present with these problems?

Thanks in advance
Lorne


Martin Höglund

unread,
Mar 22, 2002, 8:09:35 AM3/22/02
to
I've just started to use Visio for data modeling and had the same problem.
In my case I managed to get Visio to show the relationship by right-clicking
on one of the tables (the child) and choose "Show related tables". After
deleteing the relationship the erroro message dissapeared.

My best,
Martin Höglund


"LP Redmond" <lorne_...@adp.NOSPAMcom> wrote in message
news:#K8eS6#sBHA.2356@tkmsftngp07...

cavp...@gmail.com

unread,
May 28, 2014, 12:18:52 PM5/28/14
to
Martin's solution worked for me wonderfully =)
There were some relationships I wasnt seeing. Deleted them and the error disappeared.
0 new messages