Hi!

If I try to import a table in sql server 2000 sp3 enterprise manager,
choosing my access 2000 database as source and my sql server as destination,
when I hit Next, EM just goes down. In the Eventviewer Application log i can
see this:
Faulting application mmc.exe, version 5.2.3790.0, faulting module
msjet40.dll, version 4.0.8618.0, fault address 0x000d10cb.

There seems to be a problem with connecting to the Access database when
trying to make a new package. The access database works, but we are not able
to make new packages. Old packages work though. We have tried to resolve the
issue, but with no luck.

Thanks!!

Henning

Is this only with the Access connection?

Can you create packages using any other type of connection?

What about creating a link to the .mdb through another
tool like Excel?

If the latter works then it soinds like something in DTS
got whacked so you may want to reregister the DTS dlls

http://www.sqldts.com/default.aspx?225

Hi again!

I completly forgot to write that it works with any other access 2000
database. It is just this one, "large" access database that is causing
trouble. Can it be that the database is too large. It is approx. 225 Mb when
not compressed. Doesn't matter if I try to compress and repair either(still
over 200 Mb). The database has been in use for several years now. It resides
on a network share, the same as it has since it first was in use.

I wish I knew when the problem arised, but I do not. Therefore I cannot see
what we have done in order to cause this problem. We upgraded too Office 2000
quite a while ago, and it worked after that. For a long period of time we
experienced that the access database in question had to be repaired several
times a day. In the end, it was unrepairable. We had to make a new database
and was able to import the items from the corrupted access base. Now we
sometimes still experience that the database needs repairing, but not as
often.

Thanks for the quick reply!

Henning :-)

"Allan Mitchell" wrote:

Sounds like this database is causing you grief in any event!

A 225 MB Access database is no problem for SQL Server.

If this is the only DB that you are having trouble with and you have to
repair this DB often I would investigate why that happens first.

What happens if you move this Access DB from a remote network share locally?

"Henning" wrote: