>>>>Mr. Edward, Sorry to trouble u once again, But if we will use, Insert Sql at the end of add process, then how will we input the values from user.
>>>>
>>>>Pls Advs.
>>>
>>>Usually, it's doing bu user typing into textboxes, selecting from combos and so on. Isn't it?
>>
>>Yes, but how it will work without issuing append blank !! Is there other way also, If so, I will be very glad to change my class. Pls give me some example.
>
>Ok. This is basic functionality:
>1. Not to use ControlSource property, i.e. I have unbound controls.
>2. User navigates a table, firing some custom method (e.g. 'FillControls') which fills all appropriate controls with field values (resetting Textbox, etc Value properties)
>3. Pressing 'Add' or 'Edit' buttons allows user to reach controls (ReadOnly gets to .F.) and 'Add' also SetAll("value","").
>4. User interactively fills/selects controls, so he/she changes Value properties.
>5. When user click on 'Save' buttons, Button.Click event fires INSERT-SQL which collects Value properties into a record. Surely, the same event will generate unique id (primary keys) running some kind of stored procedure.

Yes, now it is clear to me, and as far as i think its much better then issuing append blank, and then tableupdate/tablerev

Thanks, I will work on it...