INSERT INTO gifts_full (giftprocdt, gifteffdat, giftbatch, gifttender, giftsolic, giftcurr, giftanon, giftpotflg, gifthnrmkr, giftchckno, giftsecure, giftsource, gifttype, giftaba, giftdepost, giftrevoke, giftfrnamt, giftbnkact, giftbnkaty, giftacctgp, giftexrate, giftsumkey, giftsec1, giftsec2,giftrest, gift8020, giftamount, giftcamp, giftcampyr, giftclass1, giftclass2, giftcomm, giftsource, giftallkey, giftid) SELECT giftprocdt, gifteffdat, giftbatch, gifttender, giftsolic, giftcurr, giftanon, giftpotflg, gifthnrmkr, giftchckno, giftsecure, giftsource, gifttype, giftaba, giftdepost, giftrevoke, giftfrnamt, giftbnkact, giftbnkaty, giftacctgp, giftexrate, giftsumkey, giftsec1, giftsec2,'sm1', 'N', 60.00, 'c ', '2014', ' ', ' ', '', 'blast ', '2605438644', '0000000264' FROM gifts_full WHERE giftkey = 2605438644
[Microsoft][ODBC SQL Server Driver][SQL Server] The column name 'giftsource' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name 'giftsource' may appear twice in the view definition.
The issue has been confirmed as a product defect and has been reported to our Research and Development team.
While a full resolution is unavailable currently, we offer the following workaround(s) in the meantime
- Delete the Source (giftsource) field from Allocation Insert / Allocation screens
Status: Please refer to KB article 4771-Scheduled fixes to see if this is scheduled for a fix.
Understanding Gift Transactions and Allocations
There is some data that is common to all of the Allocations that make up the Transaction, which you will manually enter once, using the Insert or Insert via Default form. That data will automatically be copied and will therefore be identical in all Allocations that make up the Transaction. This includes the following fields, only:
|Bank Account Type|