error in upsizing a table from access to sql server 05
Im having trouble upzizing a MS Access DB to SQL Server 2005
One table in particular keeps failing to upsize.
The table is called "master" (if that has anything to do with my error?)
The table has 1987 rows so should be able to upsize???
Im not getting any error when I try and upsize it on its own. It just comes back and says
"table was skipped or export failed"
All the other tables upsize without error.
When I try and upsize them altoghether with the same relationship etc I get the following error on a few tables all connected to the master table
Server Error 1776: There are no primary or candidate keys in the referenced table 'Master' that match the referencing column list in the foreign key 'table1'.
Server Error 1750: Could not create constraint. See previous errors.
Anyone have any ideas??
One table in particular keeps failing to upsize.
The table is called "master" (if that has anything to do with my error?)
The table has 1987 rows so should be able to upsize???
Im not getting any error when I try and upsize it on its own. It just comes back and says
"table was skipped or export failed"
All the other tables upsize without error.
When I try and upsize them altoghether with the same relationship etc I get the following error on a few tables all connected to the master table
Server Error 1776: There are no primary or candidate keys in the referenced table 'Master' that match the referencing column list in the foreign key 'table1'.
Server Error 1750: Could not create constraint. See previous errors.
Anyone have any ideas??
Looks like you have a referential integrity problem.
See what table are relationated with master table and search for records that don't have a match there.
See what table are relationated with master table and search for records that don't have a match there.
ASKER
there is a primary in the Master table and it is an auto number
or you could chuck the upsizing tool, create your table in sql server management studio and import the data (right click on db in managment studio and click on tasks - import data)
that will save you from the grief of all these errors.
a
that will save you from the grief of all these errors.
a
ASKER
Looks like you have a referential integrity problem.
See what table are relationated with master table and search for records that don't have a match there.:::
Should it not upsize correctly if you select it not to import the table releationship but just the data??
Just out of interest??
thanks
See what table are relationated with master table and search for records that don't have a match there.:::
Should it not upsize correctly if you select it not to import the table releationship but just the data??
Just out of interest??
thanks
You are right, but this message error is about references error:
Server Error 1776: There are no primary or candidate keys in the referenced table 'Master' that match the referencing column list in the foreign key 'table1'.
What's the 'table1'?
Server Error 1776: There are no primary or candidate keys in the referenced table 'Master' that match the referencing column list in the foreign key 'table1'.
What's the 'table1'?
ASKER
Its just another table I was referring to. I get that error 9 times all referencing the master table and other tables.
All facts are pointing to that being the error cause they all upsize perfectly when the master table is not included
All facts are pointing to that being the error cause they all upsize perfectly when the master table is not included
And when you add table 'master' the error is "table was skipped or export failed"?
ASKER
yes
I found this article http://support.microsoft.com/default.aspx/kb/153034
See if it helps you.
Good luck.
See if it helps you.
Good luck.
ASKER
No I had already come across this article. It does not apply to my case
thanks
thanks
Maybe you know this article too, but...
http://support.microsoft.com/default.aspx?scid=kb;EN-US;241743
http://support.microsoft.com/default.aspx?scid=kb;EN-US;241743
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
note: the above are examples that should be done separately. That is not one procedure.
Try an Autonumber field called "idx" and make it a key field.