Are you using transactions? Has the table containing the PK's actually been committed prior to entering the child tables' records?

~~Bonnie



>I put all the records in to the tables with PKs only first, then I start putting the records for the tables with FKs in.
>I should say that this is a dump. I am grabbing all the records from the main database, Not SQL Server, and dumping it into SQL Server by table, record by record.
>
>In the error log, I know that I am putting tables with FKs in the correct order, because one table that has a FK errors out, which causes the table that has a FK to it to error out.
>
>>Are you sure you've put in the parent record, with it's PK, first? And then added the child record with the correct FK? In that order.
>>
>>~~Bonnie
>>
>>
>>>I am using VFP 6 SP5, SPT to insert records in to SQL Server 2000. I just added PKs and FKs to the database. I looked at the database that these records are coming from and everything looks fine. I checked the FK references and the key is in there, but I get the conflict error.
>>> How do I get away from this other then telling everyone that they can not have FKs. and throwing the FKs out.
>>> Is there a better way to do this?
>>>
>>>Thanks,
>>>Beth