Thanks, Marcia. I now need to contact my former colleagues and let them know about the problem. I'm wondering, what kind of impact would we have if leave it without change? Or if we change, we would need to recompile each application and make certain, that every application uses AddNew (do you think, it's a good name with no possible future conflict?) and not Add - sounds like a lot of work, since we have ~40 different applications with lots of forms.

>Hi Nadya.
>
>So, I wanted to find out the problem and took out code from Add method of the form (this is a custom method of our base form class). The form still has problems, but now when I want to put the code back I see an lparameters statement with 4 parameters eItem, cKey, eBefore, eAfter. They look like some internal MS parameters (I'm sure, we would never name parameters like that). So, do we have some name conflict here?
>
>Yes. When The collection class was added to VFP in version 8, ADD became a reserved word (it is a method of the collection class). You need to change the name of your method to something else - AddNew() maybe.
>
>I remember when we moved from FPW 2.6 to VFP 3.0 - many people had the same type of problem because before buffering was introduced, they had variables called OldVal and CurVal to handle update conflicts < s >.