>>>>The situation is like this. I have a form with a parent-child
>>>>table. The child table is shown in the grid. When the user wants
>>>>to add a record, I change the control source of the parent table to the memory fields.(I am using
>>>>table buffering ).
>>>
>>>Alarm bells are going off in my head when I read this line. Why do you need to change
>>>any control sources? Why are you using memory fields and Table Buffering? If you're
>>>using buffering, you should be able to work directly with the table fields, and Fox
>>>will handle whether they're in memory or on disk.....
>>
>>Bells have broken loose in my head. The problem is I am too afraid to try on the table buffering to handle everything
>>I tried it once and I was gettig strange results and after that I never tried. The main problem is the primary key
>>validation. I accept the view of surrogate keys but the users want a sort of their own key and it has to be
>>also unique. In my experiment with buffering, I was not able to validate the fields before the user leaves the
>>control. Somehow I dont understand how all of you are using it. May be I am too dumb to understand.
>>
>>Thanks for the reply.
>>
>>alex
>
>Alex,
>If your VALID returns .F. no one is going anywhere.
>You can also return a number to get you where you want.
>Using This.Value for your validation rules is fine.

Thanks. I did it once and I got into big problems. I was not able to come out of the valid without injury.
Thank you very much.

alex