Updating from MSSQL -- MIDRANGE-L

Subject: Updating from MSSQL
From: Billy Waters <bwaters@xxxxxxxxxxxxxxxxxx>
Date: Tue, 26 Jan 2016 18:03:11 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

update XXXXX.XXXXX.BILLY.TST921L1 set SIRATE =
(select TRATE from WFK_PAYRATES_TEMP
where TEMPLY = SIEMP#)
where exists(select * from WFK_PAYRATES_TEMP
where TEMPLY = SIEMP#)

OLE DB provider "MSDASQL" for linked server "MOPICO" returned message "Key column information is insufficient or incorrect. Too many rows were affected by update.".
Msg 7343, Level 16, State 4, Line 1
The OLE DB provider "MSDASQL" for linked server "MOPICO" could not UPDATE table "[xxxxx].[xxxxx].[BILLY].[TST921L1]".

Both files have keys TEMPLY and SIEMP# TST921 is journaled.
Any help appreciated.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Updating from MSSQL , Luis Rodriguez

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.