Quite possibly. It was a shot in the dark suggestion. :-) I did not have time to test it so don't know. But it was worth a shot if it worked out in his case. I'm with Doug though, no field name should have a colon in it, IMO. :-)

>Bill, IMHO when the data on the backend dBase table is updated, it's still gonna bomb out when it tries to issue an UPDATE - SQL internally because of that field name.
>
>>INSERT INTO MyTable VALUES ( Val1, Val2, ... )
>>so you don't have to reference the troublesome field name directly?