I didnt see the line of code you referred to, but at the end of SDTMgr.HowToSyncTable there's an ASORT on an array that holds the DROP and ADD action items. It sorts so that the ADDs happen first, per your code comment about avoiding the issue of potentially dropping all fields out of the DBF structure. I changed the ASORT to perform a descending sort and it looks like it fixed the issue of "too many columns". I'll just have to remember the issue you noted. Thanks for your help on this.

>Hi Chris.
>
>>I suspected that the ADDs were taking place before the DROPs. That explains the error. Any chance of a 'DropBeforeAdd' switch? Is that feasible?
>
>Try this: near the end of SDTMgr.HowToSyncTable is this statement:
>
>

if laToDo[lnI] <> 'drop column'

>
>Change it to:
>
>

if laToDo[lnI] <> 'add column'

>
>and see if that works for you.
>
>>Anyway, thanks for a great product. Highly recommended.
>
>Thanks for the kind words.
>
>Doug