Access/Enterprise Manager Diagrams Incompatible?

  • Thread starter Thread starter Jon
  • Start date Start date
J

Jon

I asked this one a while back but I still haven't got it figured out yet.
What my problem boils down to is that SQL server diagrams created with
Access XP (latest version with patches) created through an ADP and diagrams
created with enterprise manager (latest version + patches) seem to be
completely incompatible. Whenever I open a diagram created with one tool in
the other tool, the tool doing the opening crashes, completely crashes at
that. I'm working on a project and the DB is growing to a complexity where I
really need a reliable way to share the diagrams with my team members. I
don't want to put too much work into good diagrams with one tool if they're
going to be useless in the other. Other developers I have spoken with don't
seem to have this problem. Have I missed a patch? Is this a known
incompatibility? Is something configured wrong? I'm at wits end.

Sorry for the cross posting but this anomaly is really annoying me and we
need to use both Enterprise Manager and Access and this is holding us up
somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
advance to anyone who can give me a clue on this one!


Jon
 
I have used both interchangeably without a problem. It would seem a drastic
step to start uninstalling/reinstalling without knowing exactly what the
problem may be or if it will be cured. I suggest just creating and viewing
all the diagrams in Access because everyone should have that installed.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Which version of Access do you use? Access2002(XP) or Access2003? Since I
have the same problem with SQL Server2000(Developer edition) and AccessXP,
i.e. Diagram created in one program crashes othe other program when opening.
I just wonder whether Access 2003 has the same problem or not. At least,
with AccessXP, it is not "Just me" thing.
 
I'm on Access XP, I also have 2000 installed I bet it would be the same
there though. I'd have to check to be sure. Yeah it looks like some of us
have this problem and some aren't, I'm hoping that someone knows something
as I'm really starting to like ADPs but I need this to work correctly. I
really don't want to go through the whole reinstall rigmarole either as it's
a huge time sink and I have real work to do(plus like you all said there's
no guarantee that it will fix anything).

Jon
 
I forgot to mention that the diagram created in Enterprise Manager also
crashes Visual Studio2003, if I try to open it in Server Explorer. So, the
problem seems from Enterprise Manager, rather than AccessXP. As I said, I am
using SQL Server2000 developer edition with SP3.
 
Ditto here on the SQL config....SQL 2000 developer edition with SP3 applied.
Although I tried it with enterprise edition and got the same bad results.


Jon
 
There's a thread on microsoft.public.sqlserver.server called "Diagram Editor
doesn't work in SQLServer 2000", it says something about a dll conflict
caused by installation of VB6. I do have VB 6 installed so I wonder if this
is the culprit. What do you all think? I'm not fooling with my registrations
until I know what's up with this. What do you all have installed? Any
suggestions.

Jon
 
I don't think there's any question but that it is a DLL conflict, Jon. The
issue is, of course, which DLL, and what to do about it.

I had problems with the diagram editor on my old PC, which had Visual Studio
6 (including VB6) installed. I do not have problems on my new PC, which has
never had Visual Studio 6 installed. So yes, it would seem likely that the
problem DLL is installed by Visual Studio 6. But that doesn't rule out the
possibility that it may also be installed by other applications.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
 
Well I broke down and sent a support email to MS. Maybe I'll get lucky and
get a good quick response back from them on this one. This thing is driving
me nuts!



Jon
 
Back
Top