Josh,

Thanks again for your reply.

>>Are you running AERROR() after the TABLEUPDATE() or after you move the record pointer?

^^^ After tableupdate()

>>The update conflict usually means there's a primary key issue. Are you sure >>you've designated the right field as the primary key and that it's actually >>the primary key for the table? Are you changing the primary key?

I want to be real clear on this since this may just be my problem. The remote table is a btrieve table belonging to the Platinum Accounting System. I don't set or maintain those keys, but I am able to see what they are. Below is a short view of the data dictionary list of this file with indexes at the top:

Where you see . I cut a few fields out of the list(in this email) to save space.
.
.

Platinum Dictionary - K:\PLATINUM\PFWRES\MASTER\PLATINUM.PDD
===========================================================================
Description:Oelin

INDEX #UNIQUEMOD NAME OFFSET LENGTH CASE DESC
===========================================================================
0 No Yes
Ordno 0 5 No No
1 No Yes
Itemkey 0 18 No No
Ordno 0 5 No No
2 No Yes
Sysdocid 0 4 No No
Syslinsq 0 2 No No
3 No Yes
Origsysid 0 1 No No
Origdocid 0 4 No No
Origlinsq 0 2 No No


FIELD NAME CAPTION OFFSET LENGTHTYPE
===========================================================================
Ordno OrdNo 0 5 String
Itemkey ItemKey 5 18 String
Desc Desc 23 40 String
Location Location 63 5 String
Unitprice UnitPrice 68 8 Double Bfloat
Qtyord QtyOrd 76 8 Double Bfloat
.
.
.
Reference Stewlane 203 20 String
Testfld Testfld 223 10 String


The field I added is testfld (the last one). I updated the dictionary after adding the field and used the updated dictionary in my ODBC connection. Now, to address your 'primarary key' question...

>> Are you sure you've designated the right field as the primary key and that
>> it's actually the primary key for the table? Are you changing the primary >> key?

Based on what the dictionary shows, I'm not sure what the primary key is. Since its an Order Entry Line Item Detail Table, I might assume its 'ordno, line#'.

In VFP's view designer, no keys were highlighted as in place. IOW, View Designer did not show any fields as keys in the listing. I specified that 'ordno' was a key in the view and then that 'testfld' was writeable (checkmark in the pencil column).

Can you tell what I should be doing in View Designer based on the dictionary printout and the description of the problem as you now understand it?

I appreciate your offer of assistance.

Stew