🚀 go-pugleaf

There is a known problem using ERwin with Access when system.mdw has
been modified to assign an owner other than the default dbo.  (Use the
Workgroup Administrator app to determine which system.mdw you are
using.)  Also, ERwin typically looks at the system.mdw file on your
local hard disk, so if you are actually using a system.mdw on a network
drive (e.g., to support a small multi-user Workgroup using different
networked PCs), you can also have this problem.

Incidentally, if you are trying to reverse engineer a third-part Access
application that has been compiled, you can pretty much forget that if
the developer has limited rights to view design.

Logic Works (okay, Platinum) is aware of these problems and may have
provided a solution in ERwin 3.5.x and later.  If you've got tech
support from Logic Works/Platinum, I'd certainly give them a call.  I
don't know if they ever decided to set up news groups for self-help
(well, if I was charging what they charge for annual support, I probably
wouldn't want to), but there are also ERwin User Groups in most of the
larger metropolitan areas that may be of assistance.

I'd also hit MSDN Online at www.microsoft.com and find out exactly what
error 340 is.  Is it coming from Access or the VB code in ERwin or from
the ODBC Administrator?  Sorry, I can't be more help; it's been a while
since I did any really serious work in Access.

--
Regards,
     Joseph V. Morris
     jvmorris@erols.com

In addition to responding to the NG, a personal CC is always
appreciated.

Shark Attack wrote in message <7a7mdv$iv8$1@m2.c2.telstra-mm.net.au>...
>Frank,
>Thank you for your response. The problem seems to happen everytime
ErWin has
>to access a Microsoft Access Database and doesn't seem to be related to
a
>datatype problem.
>
>For example, if I try to reverse engineer an Access Database, after you
>choose the source database, ERWin try to connect to it and brings a
message
>box saying Error 340. Then it bring an Access Connection dialog box
asking
>for a username and a password. Any name/password combination make the
>program crash (included admin and a blank password which is the
default).
>
>Same thing happens when i try to create a brand new Access Database
from a
>model. Even if the model only contains one table with one field
(Text(18)).
>
>It seemed to either be a major bug in Erwin or maybe I've got an
>incompatible version of the DAO dll.
>
>Any info on that ?
>
>Cheers
>
>Frank wrote in message <7a001k$aij$1@camel29.mindspring.com>...
>>The same concept should apply to Access.  Erwin will happily put in
>whatever
>>text you supply for the datatype.
>>
>>Frank
>>
>
>
>