Hi David.

No problem. :) Been there, done that. <bg>

>Sergey,
>
>Thanks for the catch. I had view requery on my mind yesterday, that's what I get for answering questions before my first glass of OJ. *g*
>
>>Your's workaround is correct but you're mistaken about the cause of the problem. The SQL command excuted in a method of the form/class runs in the context of this method and can access properties of the form/class. It's a bug in UPDATE command that property referenced in SET on the right side of "=" sign generates an error. Run following code and click on Command1 button to see that the first two SQL commands have no problem referencing form properties.