Data Compare Questions

Neil Davidson

Lenard,

I'm going to send you a patch direct which should fix the first problem you
are having.

I'll raise the second issue as something for us to look into.

Yours,

Neil Davidson
"lenardd" <lenardd__nospam__@hotmail.com> wrote in message
news:xfpskjEtDHA.1268@server53...
> Hi,
>
> Lets assume I have "A" database and "B" database. In the A database, I
have
> 26 records and in the B database I have 24.
>
> My "compare key" is set on the ID field (primary key). If I compare
> "missing records", it detects the 2 missing records in B. No problem
here.
> If I ALSO select the "different records" to compare option, things get
> really wacky. It now says I have 26 records that are different. This is
> not true. Differences should only be done on the records with the same
ID.
> After all, isn't that why I specified my "compare key" at the beginning of
> the wizard? As it works now, it starts the compare with the two missing
> records which don't exist in B. This makes no sense at all or am I
missing
> something?
>
> My workaround is to do the "missing records" option first and later the
> "different records" option. If this is the case, why allow the user the
> option to pick them at the same time?
>
> Also, when the "missing records" option is selected, why does the option
> "Columns to compare" determine which fields will be scripted for the
INSERT
> statement? In my case, I want to compare certain fields but insert the
> whole record (ie. all fields). Why don't you have a column (say "Columns
to
> Insert) for this?
>
> Thanks.
>
> --Lenard
>
>