Thanks for humoring me :). D*mmit. I wish I had more ideas, but right now all I think to do is make sure that the backend isn't causing/controlling the conflict with a rule of some sort. Do you have a database administrator for your backend? Or did they dump that on you, too?

P.S. Are you sure you didn't misspell your company name? Shouldn't it be Thousand Trials (lame joke).

>>Is "location" *really* the unique, primary key (ID) field in the backend data
source? I ask because '_id' in a field is usually what we (geek programmers < s >) call our key fields.
>Location is the unique field. This is a database for a document scanning system with the doc_id being the account number the doc pertains to and can have many doc_id's for each account. The location assigned is unique for each doc.
>
>Sample data:
>Doc_id Date Location
>546111111 03/24/99 000001.N01
>546111111 03/24/99 000002.N01
>546111112 03/24/99 000003.N01
>
>>Can you change the date field and not receive the error?
>
>I get the same error when I change the date field.