If your tables do not have a large number of columns, a fairly easy way is to....
Create temp view CheckView ( UniqueColumn , CheckData ) + as Select UniqueColumn , (textcol1 + textcol2+ ( CTXT (datecol1)) + ( CTXT (Integercol1)) +...) + from YourTable1 Create temp view CheckViewA ( UniqueColumn , CheckData ) + as Select UniqueColumn , (textcol1 + textcol2+ ( CTXT (datecol1)) + ( CTXT (Integercol1)) +...) + from YourTable2 Create temp view ChangedView ( UniqueColumn ,CheckData1,CheckData2) + as Select t1. UniqueColumn , t1. CheckData , t2. CheckData from CheckView t1, CheckViewA t2 + where t1. UniqueColumn = t2. UniqueColumn and t1. CheckData <> t2. CheckData Browse all from ChangedView ---Will give you the records that have been changed and you can compare the two. This assumes that you have at least one unique column that cannot be changed by the operator. If your tables have a large number of columns, it may exceed the view size limit as well. If not, any easy method. -Bob ----- Original Message ----- From: "Alastair Burr" < alastair .burr@ ntlworld .com> To: "RBASE-L Mailing List" < rbase -l@ rbase .com> Sent: Tuesday, June 8, 2010 7:21:37 AM GMT -06:00 US/Canada Central Subject: [RBASE-L] - Re: Record-To-Record Equality Test? How about creating/projecting a temp table with a primary key that includes all the (relevant) columns. Load your row(s) from one database then attempt to load the equivalent row(s) from the second database. Any rows that succeed are not the same while any that fail are. Regards, Alastair. -------------------------------------------------- From: "Wills, Steve" < jswills @ uthsc . edu > Sent: Tuesday, June 08, 2010 11:32 AM To: "RBASE-L Mailing List" < rbase -l@ rbase .com> Subject: [RBASE-L] - Record-To-Record Equality Test? > Does anyone know of a means to compare two records, in toto , for > equality||inequality? > > The records have exactly the same structure, including column names and > PK, and have a 1:1 relationship. > > One record comes from a local table and represents the data as it was at > its original INSERTion or most recent UPDATE. The other record is in a > view, populated by the data as it currently exists in a production > database. It might or might not have changed since the most recent > refresh of the local data. > > I would like to find a way to take a "management by exception" approach to > by means of a record-by-record comparison between the pair of records. > Then, if there is a difference, dig into the nature of the inequality. > > IOW , for any PK, is # RecordInLocalTable = # RecordInProductionView ? If > equal, get next PK-matched pair of records. If not, then lather, rinse, > repeat. > > Thanks, > Steve in Memphis > >
