MS Access data conversion - upsizing access 2002 database to SQL Server 2000

Author

upsizing access 2002 database to SQL Server 2000 - fatal errors

Jon

2005-04-20, 7:24 am

Hi,
I am trying to upsize an access database (about 200meg compacted) to sql
server 2000 using the upsizing tool. The wizard does not complete and kicks
me out asking to send the error report to microsoft. the error in event
viewer is:

Faulting application msaccess.exe, version 10.0.6501.0, faulting module
msjet40.dll, version 4.0.8618.0, fault address 0x000d10cb

can anyone point me in the right direction?

Thanks,

Jon

Jon

2005-04-20, 7:24 am

I should also have said this happens when creating extending properties for
one of the tables

Thanks,

Jon

"Jon" wrote:

> Hi,
> I am trying to upsize an access database (about 200meg compacted) to sql
> server 2000 using the upsizing tool. The wizard does not complete and kicks
> me out asking to send the error report to microsoft. the error in event
> viewer is:
>
> Faulting application msaccess.exe, version 10.0.6501.0, faulting module
> msjet40.dll, version 4.0.8618.0, fault address 0x000d10cb
>
> can anyone point me in the right direction?
>
> Thanks,
>
> Jon
>
>

Alex

2005-04-20, 9:25 am

Hi Jon,

Have you tried to upsize without importing the data?

Most of the time it fails because of bad data, but your error is not
being trapped as it is closing access, make sure you have the latest
fixes and updates for office http://office.microsoft.com goto to 'check
for updates' top right hand side. Also make sure you have the latest
MDAC on your computer http://www.microsoft.com/data.

Is the SQL server located on your computer you are running the upsizing
wizard?

Make sure that you are running SP3 for SQL server as well
http://www.microsoft.com/sql

If all else fails try and upsize everything else other than the
offending table, and you may have to create and import manually. After
updating all the components do a compact and repair on you database,
also try creating a blank database and importing everything from the
problematic database into the new one and try and upsize that.

Hope it helps.

Regards

Alex

Sponsored Links