Access crashes when trying to migrate db to mssql

[leonard613]

i'm not really trying to use adp but this is the closest newsgroup i could
find for my issue. what my intent is to migrate my access tables to sql
server and then link them back to access as a front end.

i'm using xp pro with office pro 2007. diagnostics on access 2007 all ok.
dbs all compacted and repaired. but...

when i try to migrate a table to mssql 2005, access immediately disappears
(crashes) when i press the "sql server" button in "move data" from the
"database tools" ribbon tab.

can anyone help me out here? anyone?

tia

 

[Sylvain Lafontaine]

No problem here when I test with a full installation of Office 2007 on WinXP
Pro SP2. When you did install Access/Office 2007, did you make a full
installation or if some parts of it - like the Upsizing Wizard - have been
installed with the option of "Install on first run" or something like that?
The "Install on first run" has been a source of many problems in the past.
Did you make a test with a brand new database file with a single table in
it? Does your table has a primary key? Did you try with the ACCDB or the
MDB format?

The SQL Server Migration Assistant for Access (SSMA Access or SSMA-A) is
another tool that can be used for migrating the schema (design) and data
from an Access database to a SQL-Server:

http://www.microsoft.com/sql/solutions/migration/access/default.mspx

There are also tools on the market for doing this job:

DBConvert for Access & MSSQL:
http://dbconvert.com/convert-access-to-mssql-pro.php

DBSync for Access & MSSQL:
http://dbconvert.com/convert-access-to-mssql-sync.php?DB=6

I never used any of these tools (including the SSMA-A) personally but you
loose nothing to try them.

Finally, if none of these work, maybe you will have to make the job by hand:
create the table manually on the SQL-Server, link them and then transfert
the data using the linked tables. Finally, there is a newsgroup for
upsizing problems: m.p.access.sqlupsizing but I don't know if you will find
help there because you seem to have more a problem of corruption or of a bad
installation of Office 2007 than anything else.