Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upsizing from Access 2000 using upsizing wizard??

Status
Not open for further replies.

jgoodman00

Programmer
Jan 23, 2001
1,510
I have just run the upsizing wizard on our access database & tried to upsize our whole database to a SQL server (MSDE) database combined with an Access 2000 project (frontend). All the standard options were enabled, in particular it was told to upsize the tables & their data. For some reason only two of the upsized tables actually contain any data, with every other table (of approx 45) being empty. The report it creates at the end states the upsizing wizard had problems creating some of our queries, but it does not state any problems in creating the tables...


Does anyone have any idea why it would do this, & if so what the solution is. I am wondering if it has to do with relationships, whereby the first two tables listed (namely adopt & annotate) are not related to any other tables with referential integrity enforced. They are also the first in the list when sorted alphabetically. All the remaining tables in some way relate with another table, & almost always with referential integrity, so I am wondering whether the referential integrity is stopping the wizard from beign able to import the data, although I would expect it to flag this problem in the report, ARRGGHHH!
James Goodman
j.goodman00@btinternet.com
 
Ok,
I have spent approx 1 day trying to upsize different combinations of tables, & then testing to see if it successfully upsizes the tables & the data. If I select approx half of the tables the upsizing executes with no trouble & all my data remains intact. However there is no order as to which tables trigger the deletion of all records in all tables, so this problem seems almost impossible to track down. I can successfully create a SQL server database & then manually import all the of the tables with no difficualty whatsoever. I would happily do this, & recreate all of the queries & stored procedures myself. However when I import the tables, it loses the primary keys for the tables, & no triggers are imported to keep the data integrity between related tables (I am not even sure if the relationships are imported).

What suggestions do people have for migrating our database, & what difficulties have people had using the various methods???? James Goodman
j.goodman00@btinternet.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top