>>>Does it not work if you put the alias before each field (Ie, instead of myField always use myTable.myField to see what happens.
>>
>>So far, no luck with that. I put the alias on each field in the select command and manually specified the updatecmd preceeding each field with the alias.
>>
>>I've also tried changing fieldname in the selectcmd (select invalidfieldname1 AS validfieldname1..), letting VFP automatically generate the updatecommand and that still didn't work (AERROR shows syntax error).
>>
>>Nuts.
>
>Could you post UpdateNameFields and Updateble FIeldList priperties?
>
>If you have:
>SELECT Fld1, InvalidFieldName AS ValidName ...
>in SelectCmd
>Then UpdatableFieldList should be:
>Fld1, ValidFieldName
>and UpdateNameList should be:
>Fld1 TableName.Fld1, ValidFieldName TableName.InvalidFieldName
>
>NOT TESTED AT ALL.

My selectcmd..

select ACTIVITY.BILLABLE, ACTIVITY.CLICODE, ACTIVITY.DATE as xdate, ACTIVITY.DESC as xdesc, ACTIVITY.DOMAIN, ACTIVITY.GROUP, ACTIVITY.NOTES, ACTIVITY.RADACID, ACTIVITY.SEND, ACTIVITY.SEQ, ACTIVITY.TIME as xtime, ACTIVITY.TYPE as xtype from ACTIVITY where clicode = (?thisform.clicode) order by clicode,seq

my updatablefieldlist..

billable,clicode,xdate,xdesc,domain,group,notes,radacid,send,seq,xtime,xtype

my updatenamelist..

billable activity.billable,clicode activity.clicode,xdate activity.date,xdesc activity.desc,domain activity.domain,group activity.group,notes activity.notes,radacid activity.radacid,send activity.send,seq activity.seq,xtime activity.time,xtype activity.type