Comments
2 comments
-
Hi Terry,
This could happen if you are either ignoring indexes in SQL Compare, or ignoring the names on constraints and indexes. Data Compare actually tries to match the constraints and indexes by name when verifying that an eligible comparison key index exists in both databases.
Changing the 'ignore indexes' and/or 'ignore the names of constraints and indexes' settings in SQL Compare and synchronizing the schema will fix the problem. -
I found that the problem was there was no primary key (Access programmers
) )
Thanks!
Add comment
Please sign in to leave a comment.
Am I doing something wrong, or is this a SERIOUS bug?